CVE-2026-25153

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Backstage is an open framework for building developer portals, and @backstage/plugin-techdocs-node provides common node.js functionalities for TechDocs. In versions of @backstage/plugin-techdocs-node prior to 1.13.11 and 1.14.1, when TechDocs is configured with runIn: local, a malicious actor who can submit or modify a repository's mkdocs.yml file can execute arbitrary Python code on the TechDocs build server via MkDocs hooks configuration. @backstage/plugin-techdocs-node versions 1.13.11 and 1.14.1 contain a fix. The fix introduces an allowlist of supported MkDocs configuration keys. Unsupported configuration keys (including hooks) are now removed from mkdocs.yml before running the generator, with a warning logged to indicate which keys were removed. Users of @techdocs/cli should also upgrade to the latest version, which includes the fixed @backstage/plugin-techdocs-node dependency. Some workarounds are available. Configure TechDocs with runIn: docker instead of runIn: local to provide container isolation, though it does not fully mitigate the risk. Limit who can modify mkdocs.yml files in repositories that TechDocs processes; only allow trusted contributors. Implement PR review requirements for changes to mkdocs.yml files to detect malicious hooks configurations before they are merged. Use MkDocs < 1.4.0 (e.g., 1.3.1) which does not support hooks. Note: This may limit access to newer MkDocs features. Building documentation in CI/CD pipelines using @techdocs/cli does not mitigate this vulnerability, as the CLI uses the same vulnerable @backstage/plugin-techdocs-node package.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.6% × 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.6%
EPSS %ILE
48th
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

January 30, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
Patch available. Sources: github, redhat.
Red HatMentions a patch (unverified)
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25153.json
Red Hat

2435576 – (CVE-2026-25153) CVE-2026-25153 @backstage/plugin-techdocs-node: @backstage/plugin-techdocs-node vulnerable to arbitrary code execution via MkDocs hooks

https://bugzilla.redhat.com/show_bug.cgi?id=2435576
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-25153
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6802
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6174
GitHub advisoryMentions a patch (unverified)

Arbitrary code execution via MkDocs hooks in TechDocs · Advisory · backstage/backstage · GitHub

https://github.com/backstage/backstage/security/advisories/GHSA-6jr7-99pf-8vgf

Vendor Advisories for CVE-2026-25153(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17751406472026-04-07redhat
redhatrhdh/rhdh-hub-rhel9:17745456052026-03-30redhat

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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@backstage/plugin-techdocs-node1.14.0
  • 1.14.0 up to 1.14.1: fixed in 1.14.1
  • every version up to 1.13.11: fixed in 1.13.11
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 29× 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 95 of 194 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25153?
CVE-2026-25153 is a high-severity vulnerability; its CVE record was published on January 30, 2026. Backstage is an open framework for building developer portals, and @backstage/plugin-techdocs-node provides common node.js functionalities for TechDocs. In versions of @backstage/plugin-techdocs-node prior to 1.13.11 and 1.14.1, when TechDocs is configured with runIn: local, a malicious actor who…
When was the CVE record for CVE-2026-25153 published?
The CVE record for CVE-2026-25153 was published on January 30, 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 July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-25153 actively exploited?
CVE-2026-25153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25153?
CVE-2026-25153 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-25153?
A fix for CVE-2026-25153 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25153 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-25153

Explore →

Is Your Infrastructure Affected by CVE-2026-25153?

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

Book a Demo →Browse All CVEs