CVE-2026-6040

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory published 2026-06-15. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

A heap use-after-free existed when importing the blank-width characters of an ODF number format. A position value read from the document was not checked against the length of the format-code string, so a malformed number format could be processed against memory outside that string. In fixed versions the position is bounds-checked before use.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 15, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-6040(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuure-java (4:26.2.4.2-0ubuntu0.26.04.2) @ resolute2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libreoffice1:7.0.4-4 ... 4:7.6.4~rc1-1~bpo12+1 (402 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreoffice4:25.2.3-2 ... 4:25.2.3-2+deb13u5~bpo12+1 (8 versions)4:25.2.3-2+deb13u5
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreoffice4:25.2.3-2 ... 4:26.2.3.2-2~bpo13+1 (51 versions)4:26.2.3.2-2

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 264 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-14 03:47 UTCEG score recompute
  5. 2026-09-14 03:47 UTCVendor advisory
  6. 2026-09-14 03:47 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-30 22:59 UTCEG score recompute
  16. 2026-08-30 22:59 UTCVendor advisory
  17. 2026-08-30 22:59 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-28 21:42 UTCEPSS rescore
  20. 2026-08-26 14:47 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 23:38 UTCEG score recompute
  23. 2026-08-24 23:38 UTCVendor advisory
  24. 2026-08-24 23:38 UTCGHSA enrichment
  25. 2026-08-23 23:20 UTCVendor advisory
Show 75 more
  1. 2026-08-23 23:19 UTCGHSA enrichment
  2. 2026-08-23 09:49 UTCEG score recompute
  3. 2026-08-23 09:49 UTCVendor advisory
  4. 2026-08-23 09:48 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:44 UTCVendor advisory
  7. 2026-08-21 23:44 UTCGHSA enrichment
  8. 2026-08-21 10:46 UTCEG score recompute
  9. 2026-08-21 10:46 UTCVendor advisory
  10. 2026-08-21 10:46 UTCGHSA enrichment
  11. 2026-08-20 22:56 UTCEPSS rescore
  12. 2026-08-20 21:39 UTCVendor advisory
  13. 2026-08-20 21:39 UTCGHSA enrichment
  14. 2026-08-20 08:41 UTCEG score recompute
  15. 2026-08-20 08:41 UTCVendor advisory
  16. 2026-08-20 08:41 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-19 13:15 UTCEG score recompute
  19. 2026-08-19 13:15 UTCVendor advisory
  20. 2026-08-19 13:15 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 11:26 UTCVendor advisory
  25. 2026-08-17 11:26 UTCGHSA enrichment
  26. 2026-08-16 22:29 UTCEG score recompute
  27. 2026-08-16 22:29 UTCVendor advisory
  28. 2026-08-16 22:29 UTCGHSA enrichment
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 05:14 UTCEG score recompute
  32. 2026-08-16 05:14 UTCVendor advisory
  33. 2026-08-16 05:14 UTCGHSA enrichment
  34. 2026-08-16 02:15 UTCEPSS rescore
  35. 2026-08-15 16:17 UTCVendor advisory
  36. 2026-08-15 16:17 UTCGHSA enrichment
  37. 2026-08-15 03:19 UTCEG score recompute
  38. 2026-08-15 03:19 UTCVendor advisory
  39. 2026-08-15 03:19 UTCGHSA enrichment
  40. 2026-08-15 01:31 UTCEPSS rescore
  41. 2026-08-14 14:21 UTCVendor advisory
  42. 2026-08-14 14:21 UTCGHSA enrichment
  43. 2026-08-14 01:24 UTCEG score recompute
  44. 2026-08-14 01:24 UTCVendor advisory
  45. 2026-08-14 01:24 UTCGHSA enrichment
  46. 2026-08-13 22:00 UTCEPSS rescore
  47. 2026-08-13 12:26 UTCVendor advisory
  48. 2026-08-13 12:26 UTCGHSA enrichment
  49. 2026-08-12 23:28 UTCEG score recompute
  50. 2026-08-12 23:28 UTCVendor advisory
  51. 2026-08-12 23:28 UTCGHSA enrichment
  52. 2026-08-12 13:51 UTCEPSS rescore
  53. 2026-08-12 10:31 UTCVendor advisory
  54. 2026-08-12 10:31 UTCGHSA enrichment
  55. 2026-08-11 21:33 UTCEG score recompute
  56. 2026-08-11 21:33 UTCVendor advisory
  57. 2026-08-11 21:33 UTCGHSA enrichment
  58. 2026-08-11 08:36 UTCEG score recompute
  59. 2026-08-11 08:36 UTCVendor advisory
  60. 2026-08-11 08:36 UTCGHSA enrichment
  61. 2026-08-11 00:00 UTCEPSS rescore
  62. 2026-08-10 19:38 UTCVendor advisory
  63. 2026-08-10 19:38 UTCGHSA enrichment
  64. 2026-08-10 03:27 UTCVendor advisory
  65. 2026-08-10 03:27 UTCGHSA enrichment
  66. 2026-08-09 14:30 UTCEG score recompute
  67. 2026-08-09 14:30 UTCVendor advisory
  68. 2026-08-09 14:30 UTCGHSA enrichment
  69. 2026-08-09 13:47 UTCEPSS rescore
  70. 2026-08-09 01:32 UTCEG score recompute
  71. 2026-08-09 01:32 UTCVendor advisory
  72. 2026-08-09 01:32 UTCGHSA enrichment
  73. 2026-08-08 16:37 UTCEPSS rescore
  74. 2026-08-08 12:35 UTCVendor advisory
  75. 2026-08-08 12:35 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-6040?
CVE-2026-6040 is a high vulnerability published on June 15, 2026. A heap use-after-free existed when importing the blank-width characters of an ODF number format. A position value read from the document was not checked against the length of the format-code string, so a malformed number format could be processed against memory outside that string. In fixed…
When was CVE-2026-6040 disclosed?
CVE-2026-6040 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6040 actively exploited?
CVE-2026-6040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-6040?
CVE-2026-6040 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-6040?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6040, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6040

Explore →

Is Your Infrastructure Affected by CVE-2026-6040?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.