OSV-2026-1126 Heap-buffer-overflow in isvcd_nal_byte_swap_emulation
Not scored
Published
Check this codebase for OSV-2026-1126 and fix it if it is affected.
What it is: OSV-2026-1126 is a vulnerability in libavc, published on 8 Aug 2026.
Exploitation: There is no known exploitation of OSV-2026-1126 in the wild and no public exploit code.
Affected packages and fixed versions:
- libavc (OSS-Fuzz): affected all versions; 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/OSV-2026-1126/ (Markdown: https://insights.sbomify.com/OSV-2026-1126/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is OSV-2026-1126?
OSV-2026-1126 is a vulnerability in libavc, published on 8 Aug 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=543374000
Crash type: Heap-buffer-overflow WRITE 4
Crash state:
isvcd_nal_byte_swap_emulation
isvcd_nal_parse_vcl_nal_partial
isvcd_pre_parse_refine_au
Which versions are affected by OSV-2026-1126?
1 open source package ship an affected version, including libavc.
| Package | Affected | Fixed in |
|---|---|---|
libavc OSS-Fuzz | All versions | None |
How do I fix OSV-2026-1126?
No fix has been published for OSV-2026-1126 yet. Limit exposure of the affected software until one is available.
Is OSV-2026-1126 being exploited?
There is no known exploitation of OSV-2026-1126 in the wild and no public exploit code.