CVE-2026-44179

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-22. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-112144 (ENISA EUVD) · GHSA-w56x-9778-rppx (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Remote Macros provides XWiki rendering macros that are useful when migrating content from Confluence. From 1.13 until 1.14.5, the excerpt-include macro does not properly escape the included page's title and executes excerpt content with the macro's rights. The title handling in xwiki-pro-macros-ui/src/main/resources/Confluence/Macros/ExcerptInclude.xml and the rendering of excerpt content into XWiki syntax both allow syntax injection. Any user able to edit a page, even without script or programming rights, can supply executable macro syntax in the title or excerpt and cause remote code execution when the page is included. This affects confidentiality, integrity and availability of the whole XWiki installation. This issue is fixed in version 1.14.5.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

June 22, 2026

Last Modified

November 2, 2026

Advisory Details (2)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Remote code execution from page title and content via excerpt-include macro · Advisory · xwikisas/xwiki-pro-macros · GitHub

https://github.com/xwikisas/xwiki-pro-macros/security/advisories/GHSA-w56x-9778-rppx
GitHub commit

commit 151d4fccb62f (xwikisas/xwiki-pro-macros)

Fix landed in xwikisas/xwiki-pro-macros commit 151d4fccb62f — awaiting tagged release

https://github.com/xwikisas/xwiki-pro-macros/commit/151d4fccb62f6ec5f3c972e837869454677ab1ca

Vendor Advisories for CVE-2026-44179(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 / EcosystemFix (by version range) / PatchReleasedSource
mavencom.xwiki.pro:xwiki-pro-macros @ 1.14.5 (fixes >= 1.13, < 1.14.5)—ghsa

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.xwiki.pro:xwiki-pro-macros—
  • 1.13 up to 1.14.5: fixed in 1.14.5
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-13 13:19 UTCEchelonGraph re-scored
  3. 2026-11-13 13:19 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-12 13:59 UTCEchelonGraph re-scored
  6. 2026-11-12 13:59 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-11-11 14:44 UTCEchelonGraph re-scored
  9. 2026-11-11 14:44 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-11-10 15:30 UTCEchelonGraph re-scored
  12. 2026-11-10 15:30 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-11-09 16:14 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  15. 2026-11-08 16:56 UTCEchelonGraph re-scored
  16. 2026-11-08 16:56 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-11-07 17:41 UTCEchelonGraph re-scored
  19. 2026-11-07 17:41 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  20. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-06 18:27 UTCEchelonGraph re-scored
  22. 2026-11-06 18:27 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  23. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-11-06 08:55 UTCOSV refresh
  25. 2026-11-05 19:11 UTCEchelonGraph re-scored
Show 36 more
  1. 2026-11-05 19:11 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  2. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-04 19:55 UTCEchelonGraph re-scored
  4. 2026-11-04 19:55 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-11-03 20:40 UTCEchelonGraph re-scored
  7. 2026-11-03 20:40 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  8. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-11-02 21:25 UTCEchelonGraph re-scored
  10. 2026-11-02 21:25 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  11. 2026-11-02 20:28 UTCEchelonGraph re-scored
  12. 2026-11-02 20:28 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-11-02 13:26 UTCEchelonGraph re-scored
  15. 2026-11-02 13:26 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-11-01 14:11 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  18. 2026-11-01 07:49 UTCGHSA enrichmentGHSA-w56x-9778-rppx · GitHub severity CRITICAL · GitHub CVSS 9.9
  19. 2026-11-01 07:49 UTCEchelonGraph re-scored
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-31 14:56 UTCEchelonGraph re-scored
  22. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-30 15:41 UTCEchelonGraph re-scored
  24. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-28 16:26 UTCEchelonGraph re-scored
  26. 2026-10-28 16:12 UTCENISA EUVD ID recordedEUVD-2026-112144 · Source: ENISA EUVD
  27. 2026-10-25 14:27 UTCEchelonGraph re-scored
  28. 2026-10-18 03:39 UTCEchelonGraph re-scored
  29. 2026-10-12 16:05 UTCEchelonGraph re-scored
  30. 2026-10-11 19:47 UTCEchelonGraph re-scored
  31. 2026-10-11 17:02 UTCEchelonGraph re-scored
  32. 2026-10-11 14:27 UTCEchelonGraph re-scored
  33. 2026-07-30 19:23 UTCEchelonGraph re-scored
  34. 2026-07-26 15:58 UTCEchelonGraph re-scored
  35. 2026-07-23 03:14 UTCEchelonGraph re-scored
  36. 2026-06-22 20:36 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-44179?
CVE-2026-44179 is a critical-severity vulnerability; its CVE record was published on June 22, 2026. XWiki Remote Macros provides XWiki rendering macros that are useful when migrating content from Confluence. From 1.13 until 1.14.5, the excerpt-include macro does not properly escape the included page's title and executes excerpt content with the macro's rights. The title handling in…
When was the CVE record for CVE-2026-44179 published?
The CVE record for CVE-2026-44179 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-44179 actively exploited?
CVE-2026-44179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44179?
CVE-2026-44179 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44179?
A fix for CVE-2026-44179 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44179 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-44179

Explore →

Is Your Infrastructure Affected by CVE-2026-44179?

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