diff --git a/crates/infisearch/RUSTSEC-0000-0000.md b/crates/infisearch/RUSTSEC-0000-0000.md
new file mode 100644
index 0000000000..7ecb5b7bce
--- /dev/null
+++ b/crates/infisearch/RUSTSEC-0000-0000.md
@@ -0,0 +1,30 @@
+```toml
+[advisory]
+id = "RUSTSEC-0000-0000"
+package = "infisearch"
+date = "2024-10-13"
+url = "https://github.com/ang-zeyu/infisearch/issues/11"
+informational = "unsound"
+categories = ["memory-corruption"]
+keywords = ["out-of-bounds", "heap-buffer-overflow", "soundness", "unsafe"]
+
+[versions]
+patched = []
+```
+
+# `DocInfo::get_num_val` can read out of bounds
+
+Affected versions of `infisearch` contain a safe method,
+`DocInfo::get_num_val`, which can perform an out-of-bounds read.
+
+The method calculates an index from `doc_id` and `num_id`, but the debug
+assertion checks the computed index against the wrong backing vector. The
+method then uses unchecked indexing on `doc_i64_vals`, which can read past the
+end of the allocation when the computed index is greater than or equal to
+`doc_i64_vals.len()`.
+
+Because the method is safe, callers do not need to use `unsafe` to trigger the
+invalid memory access. The issue was reported with AddressSanitizer as a
+heap-buffer-overflow.
+
+No patched release is currently known.