# RUSTSEC-2026-0130: Out-of-bounds read/write in `Index` and `IndexMut` implementations

> Out-of-bounds read/write in Caja indexing allows memory corruption and potential code execution via safe public APIs.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2026

## What is RUSTSEC-2026-0130?

RUSTSEC-2026-0130 is a memory corruption vulnerability in caja, published on 2 May 2026. 

### Official description

The `Index` and `IndexMut` implementations for `Caja` use unchecked pointer
arithmetic without bounds validation. Creating a `Caja` with a small key and
then accessing an out-of-range index causes out-of-bounds reads or writes
beyond the allocated memory.

This can be triggered through safe public APIs — the `[]` indexing operator
on a `Caja` with an out-of-range index — with no `unsafe` required from the
caller.

## Which versions are affected by RUSTSEC-2026-0130?

1 open source package ship an affected version, including caja.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `caja` | crates.io | From 0.0.0-0 | 0.3.0 |

## How do I fix RUSTSEC-2026-0130?

Upgrade caja to 0.3.0 or later.

## Is RUSTSEC-2026-0130 being exploited?

There is no known exploitation of RUSTSEC-2026-0130 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0130 and fix it if it is affected.

What it is: RUSTSEC-2026-0130 is a memory corruption vulnerability in caja, published on 2 May 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0130 in the wild and no public exploit code.

Affected packages and fixed versions:
- caja (crates.io): affected from 0.0.0-0; fixed in 0.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0130/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0130/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0130

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0130/
Summaries are generated and may contain mistakes; the official description above is the record.