OSV-2026-311
UNKNOWN READ in strncasecmp
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=487216732
Crash type: UNKNOWN READ
Crash state:
strncasecmp
vcardcomponent_string_to_kind
_parse_vcard
What each source reports
OSV No score
UNKNOWN READ in strncasecmp
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=487216732
Crash type: UNKNOWN READ
Crash state:
strncasecmp
vcardcomponent_string_to_kind
_parse_vcard
- Record
OSV-2026-311- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libicalOSS-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-311 is a vulnerability with no CVSS score yet in libical, published February 26, 2026. No source lists public exploit code. A source reports a fix.