CVE-2026-63268

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

LibreOffice Calc can link a cell range to an external data source, and the link is saved in the document. A link of the sql type could name a folder of local text files as a database, so opening a document could read a local text file into the sheet. In fixed versions only the csv, html and xml data providers are restored when a document is loaded.

CVSS v3
6.7
EG Score
6.7MEDIUMmedium confidence
EG Risk
30
EG Risk 30/100

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 (value × EchelonGraph’s weight)
Severity67% × 45%
The EG Score, 6.7 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 5, 2026

Last Modified

October 6, 2026

Advisory Details (1)

Auto-updated Oct 5, 2026
Patch available.
generic

Security advisories — LibreOffice

https://www.libreoffice.org/about-us/security/advisories/cve-2026-63268

Vendor Advisories for CVE-2026-63268(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libreoffice4:24.2.0-1 ... 4:7.6.4~rc1-1~bpo12+1 (250 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libreoffice4:25.2.3-2 ... 4:25.2.3-2+deb13u7 (11 versions)
  • every version up to 4:25.2.3-2+deb13u8: fixed in 4:25.2.3-2+deb13u8
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libreoffice4:25.2.3-2 ... 4:26.2.4.2-2 (56 versions)
  • every version up to 4:26.2.5.2-1: fixed in 4:26.2.5.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 16:48 UTCEG score recompute
  2. 2026-10-11 14:10 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-10 23:10 UTCEG score recompute
  5. 2026-10-10 23:10 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-09 21:25 UTCEG score recompute
  8. 2026-10-09 21:25 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-08 19:40 UTCEG score recompute
  11. 2026-10-08 19:40 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-07 17:10 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  15. 2026-10-06 15:24 UTCEG score recompute
  16. 2026-10-06 15:24 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-06 15:03 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  19. 2026-10-05 13:18 UTCEG score recompute
  20. 2026-10-05 13:18 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  21. 2026-10-05 13:03 UTCEG score recompute
  22. 2026-10-05 13:02 UTCGHSA enrichmentGHSA-rvj5-mfwr-769g
  23. 2026-10-05 12:31 UTCEG score recompute
  24. 2026-10-05 11:26 UTCEG score recompute
  25. 2026-10-05 11:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63268?
CVE-2026-63268 is a medium-severity vulnerability; its CVE record was published on October 5, 2026. LibreOffice Calc can link a cell range to an external data source, and the link is saved in the document. A link of the sql type could name a folder of local text files as a database, so opening a document could read a local text file into the sheet. In fixed versions only the csv, html and xml…
When was CVE-2026-63268 made public?
CVE-2026-63268 was made public on October 5, 2026: that is the date its CVE record's CNA, Document Fdn., gives for when the vulnerability was made public. The CVE record itself was published on October 5, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-63268 actively exploited?
CVE-2026-63268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63268?
CVE-2026-63268 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63268?
A fix for CVE-2026-63268 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63268 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63268?

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

Book a Demo →Browse All CVEs