# RUSTSEC-2026-0150: audiopus_sys is unmaintained


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 May 2026

## What is RUSTSEC-2026-0150?

RUSTSEC-2026-0150 is a vulnerability in audiopus_sys, published on 21 May 2026. 

### Official description

audiopus_sys is implicitly unmaintained and holds a reference to CMake versions with which CMake 4.0 is not backwards compatible, causing cargo builds to error. An effort to contact the maintainer was made on June 10th, 2025 with no reply. A separate 2025 PR was made (from a different user) addressing the CMake 4.0 issue with no reply. The last commit to audiopus_sys is dated 5 years ago.

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

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


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

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

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

## Is RUSTSEC-2026-0150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0150 is a vulnerability in audiopus_sys, published on 21 May 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0150 in the wild and no public exploit code.

Affected packages and fixed versions:
- audiopus_sys (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-0150/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0150/index.md)
```

## Sources

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

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