OSV-2026-308
Heap-buffer-overflow in vcardstructured_new_from_string
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=486715154
Crash type: Heap-buffer-overflow WRITE 8
Crash state:
vcardstructured_new_from_string
vcardparameter_set_value_from_string
_parse_vcard
What each source reports
OSV No score
Heap-buffer-overflow in vcardstructured_new_from_string
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=486715154
Crash type: Heap-buffer-overflow WRITE 8
Crash state:
vcardstructured_new_from_string
vcardparameter_set_value_from_string
_parse_vcard
- Record
OSV-2026-308- 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-308 is a vulnerability with no CVSS score yet in libical, published February 25, 2026. No source lists public exploit code. A source reports a fix.