CVE-2026-41200

HIGHNVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st 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

Also known asEUVD-2026-25158 (ENISA EUVD)Source: ENISA EUVD

8.5EG
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.4%CVSS: 8.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

STIG Manager is an API and web client for managing Security Technical Implementation Guides (STIG) assessments of Information Systems. Versions 1.5.10 through 1.6.7 have a reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code in src/init.js and public/reauth.html. During the OIDC redirect flow, the error and error_description query parameters returned by the OIDC provider are written directly to the DOM via innerHTML without HTML escaping. An attacker who can craft a malicious redirect URL and convince a user to follow it can execute arbitrary JavaScript in the application's origin context. The vulnerability is most severe when the targeted user has an active STIG Manager session running in another browser tab — injected code executes in the same origin and can communicate with the SharedWorker managing the active access token, enabling authenticated API requests on behalf of the victim including reading and modifying collection data. The vulnerability is patched in version 1.6.8. There is no workaround short of upgrading. Deployments behind a web application firewall that filters reflected XSS payloads in query parameters may have partial mitigation, but this is not a substitute for patching.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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).

The CVE record names the fixed release. Apply it within your standard update timelines.

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

April 23, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated Apr 29, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Reflected XSS vulnerability in the Web App · Advisory · NUWCDIVNPT/stig-manager · GitHub

Affected: version 1.6.8. Users should upgrade immediately. Per project policy, only the cur

https://github.com/NUWCDIVNPT/stig-manager/security/advisories/GHSA-wg33-j3rv-jq72

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 39× 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 199 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 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-41200?
CVE-2026-41200 is a high-severity vulnerability; its CVE record was published on April 23, 2026. STIG Manager is an API and web client for managing Security Technical Implementation Guides (STIG) assessments of Information Systems. Versions 1.5.10 through 1.6.7 have a reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code in src/init.js and…
When was the CVE record for CVE-2026-41200 published?
The CVE record for CVE-2026-41200 was published on April 23, 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-41200 actively exploited?
CVE-2026-41200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41200?
CVE-2026-41200 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-41200?
The CVE record for CVE-2026-41200 names the fix: "The vulnerability is patched in version 1.6.8."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41200?

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