CVE-2025-59841

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th 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-2025-31126 (ENISA EUVD)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flag Forge is a Capture The Flag (CTF) platform. In versions from 2.2.0 to before 2.3.1, the FlagForge web application improperly handles session invalidation. Authenticated users can continue to access protected endpoints, such as /api/profile, even after logging out. CSRF tokens are also still valid post-logout, which can allow unauthorized actions. This issue has been patched in version 2.3.1.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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.4%
EPSS %ILE
34th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-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-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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 25, 2025

Last Modified

October 11, 2026

Advisory Details (2)

Auto-updated Nov 8, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Improper Session Handling Allows Access After Logout · Advisory · FlagForgeCTF/flagForge · GitHub

https://github.com/FlagForgeCTF/flagForge/security/advisories/GHSA-h6pr-4cwv-6cjg
GitHub commit Patch Available

commit 304b6c82a4f7 (FlagForgeCTF/flagForge)

Patch available: FlagForgeCTF/flagForge v2.3.1 (contains commit 304b6c82a4f7)

https://github.com/FlagForgeCTF/flagForge/commit/304b6c82a4f76871b336404b91e5cdd8a7d7d5bd

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 241 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-59841?
CVE-2025-59841 is a critical-severity vulnerability; its CVE record was published on September 25, 2025. Flag Forge is a Capture The Flag (CTF) platform. In versions from 2.2.0 to before 2.3.1, the FlagForge web application improperly handles session invalidation. Authenticated users can continue to access protected endpoints, such as /api/profile, even after logging out. CSRF tokens are also still…
When was the CVE record for CVE-2025-59841 published?
The CVE record for CVE-2025-59841 was published on September 25, 2025. 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 11, 2026; the record at its source may have been updated since.
Is CVE-2025-59841 actively exploited?
CVE-2025-59841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-59841?
CVE-2025-59841 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-59841?
A fix for CVE-2025-59841 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-59841

Explore →

Is Your Infrastructure Affected by CVE-2025-59841?

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