# RUSTSEC-2026-0299: `owned-alloc` is unmaintained

> The owned-alloc Rust crate is unmaintained, posing a supply chain risk due to lack of security updates and maintainer responsiveness.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Sep 2026

## What is RUSTSEC-2026-0299?

RUSTSEC-2026-0299 is a vulnerability in owned-alloc, published on 22 Sep 2026. 

### Official description

The `owned-alloc` crate has had no release since 2018, and the maintainer has
not responded to the upstream issue or to direct contact.

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

1 open source package ship an affected version, including owned-alloc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `owned-alloc` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for RUSTSEC-2026-0299 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0299 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0299 is a vulnerability in owned-alloc, published on 22 Sep 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0299 in the wild and no public exploit code.

Affected packages and fixed versions:
- owned-alloc (crates.io): affected from 0.0.0-0; no fix listed

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-0299/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0299/index.md)
```

## Sources

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

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