OSV-2026-860
UNKNOWN READ in write_publickey
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=519999729
Crash type: UNKNOWN READ
Crash state:
write_publickey
auth_update_binary
sc_update_binary
What each source reports
OSV No score
UNKNOWN READ in write_publickey
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=519999729
Crash type: UNKNOWN READ
Crash state:
write_publickey
auth_update_binary
sc_update_binary
- Record
OSV-2026-860- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
openscOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2026-860 is a vulnerability with no CVSS score yet in opensc, published June 6, 2026. No source lists public exploit code. A source reports a fix.