diff --git a/crates/nano_arena/RUSTSEC-0000-0000.md b/crates/nano_arena/RUSTSEC-0000-0000.md
new file mode 100644
index 0000000..ef31691
--- /dev/null
+++ b/crates/nano_arena/RUSTSEC-0000-0000.md
@@ -0,0 +1,30 @@
+```toml
+[advisory]
+id = "RUSTSEC-0000-0000"
+package = "nano_arena"
+date = "2021-01-31"
+url = "https://github.com/bennetthardwick/nano-arena/issues/1"
+categories = ["memory-corruption"]
+keywords = ["memory-safety", "aliasing", "unsound"]
+
+[versions]
+patched = [">= 0.5.2"]
+
+[affected.functions]
+"nano_arena::Arena::split_at" = ["< 0.5.2"]
+"nano_arena::ArenaSplit::split_at" = ["< 0.5.2"]
+```
+
+# split_at allows obtaining multiple mutable references to the same data
+
+Affected versions of this crate assumed that `Borrow<Idx>` was guaranteed to
+return the same value on `.borrow()`. The borrowed index value was used to
+retrieve a mutable reference to a value.
+
+If the `Borrow<Idx>` implementation returned a different index, the split arena
+would allow retrieving the index as a mutable reference creating two mutable
+references to the same element. This violates Rust's aliasing rules and allows
+for memory safety issues such as writing out of bounds and use-after-frees.
+
+The flaw was corrected in commit `6b83f9d` by storing the `.borrow()` value in
+a temporary variable.