CVE-2026-4813

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-69014 (ENISA EUVD) · GHSA-wvvp-v69c-rj86 (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

A vulnerability in the Lutece Core XSL export management module up to version 7.1.7, which allows authenticated administrators to execute code remotely. The XML/XSLT processing configuration does not enable secure processing mode (FEATURE_SECURE_PROCESSING), allowing Java extension functions to be executed from malicious XSL stylesheets. An attacker with administrator privileges can upload a manipulated XSL transformation file and trigger its execution during user export operations, resulting in the execution of arbitrary code on the server.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

September 1, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Fix referenced — no release confirmed yet.
Web page

Code injection in the Lutece Core | INCIBE-CERT | INCIBE

http://incibe.es/en/incibe-cert/notices/aviso/code-injection-lutece-core

Vendor Advisories for CVE-2026-4813(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 142× 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.

Showing the most recent 100 of 346 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-4813?
CVE-2026-4813 is a critical-severity vulnerability; its CVE record was published on September 1, 2026. A vulnerability in the Lutece Core XSL export management module up to version 7.1.7, which allows authenticated administrators to execute code remotely. The XML/XSLT processing configuration does not enable secure processing mode (FEATURESECUREPROCESSING), allowing Java extension functions to be…
When was CVE-2026-4813 made public?
CVE-2026-4813 was made public on September 1, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on September 1, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-4813 actively exploited?
CVE-2026-4813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4813?
CVE-2026-4813 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-4813?
A fix for CVE-2026-4813 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-4813 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-4813

Explore →

Is Your Infrastructure Affected by CVE-2026-4813?

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