CVE-2026-90624

CVE-2026-90624 is a high-severity vulnerability in Apache Openoffice with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

An unchecked memory access in the PDF import code of Apache OpenOffice versions through 4.1.16 on allows a crafted PDF to execute an out-of-bounds memory write. This could crash the program or cause memory corruption. Users are recommended to upgrade to version 4.1.17, which fixes this issue.

Frequently asked questions

What is CVE-2026-90624?
An unchecked memory access in the PDF import code of Apache OpenOffice versions through 4.1.16 on allows a crafted PDF to execute an out-of-bounds memory write. This could crash the program or cause memory corruption. Users are recommended to upgrade to version 4.1.17, which fixes this issue.
How severe is CVE-2026-90624?
CVE-2026-90624 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2026-90624 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-90624?
CVE-2026-90624 affects Apache Openoffice. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-90624?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-90624 published?
CVE-2026-90624 was published on 2026-11-04 and last updated on 2026-11-05.

References

Affected products (1)

More vulnerabilities in Apache Openoffice

All CVEs affecting Apache Openoffice →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →