OSV-2026-743 UNKNOWN READ in persist_target.c
Not scored
Published
Check this codebase for OSV-2026-743 and fix it if it is affected.
What it is: OSV-2026-743 is a vulnerability in libcoap, published on 16 May 2026.
Exploitation: There is no known exploitation of OSV-2026-743 in the wild and no public exploit code.
Affected packages and fixed versions:
- libcoap (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-743/ (Markdown: https://insights.sbomify.com/OSV-2026-743/index.md)
An unknown read vulnerability in persist_target.c may allow attackers to disclose sensitive memory contents.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2026-743?
OSV-2026-743 is a vulnerability in libcoap, published on 16 May 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=513282269
Crash type: UNKNOWN READ
Crash state:
persist_target.c
Which versions are affected by OSV-2026-743?
1 open source package ship an affected version, including libcoap.
| Package | Affected | Fixed in |
|---|---|---|
libcoap OSS-Fuzz | All versions | None |
How do I fix OSV-2026-743?
No fix has been published for OSV-2026-743 yet. Limit exposure of the affected software until one is available.
Is OSV-2026-743 being exploited?
There is no known exploitation of OSV-2026-743 in the wild and no public exploit code.