CVE-2025-2611

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 8.4% (95th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Weaponized

Also known asEUVD-2025-23629 (ENISA EUVD) · GHSA-3h67-687r-7fpc (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 8.4%CVSS: 9.3Exploit: MetasploitExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

The ICTBroadcast application unsafely passes session cookie data to shell processing, allowing an attacker to inject shell commands into a session cookie that get executed on the server. This results in unauthenticated remote code execution in the session handling.

Versions 7.4 and below are known to be vulnerable.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
83
EG Risk 83/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
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 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: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.
EPSS PROB
8.4%
EPSS %ILE
95th
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS
EG Likelihood
8.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: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.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).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.

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

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

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

August 5, 2025

Last Modified

November 8, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
Web page

ICTBroadcast <= 7.4 Unauthenticated Session Cookie RCE | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ictbroadcast-unauthenticated-session-cookie-rce
Web page

ICTBroadcast Command Injection Actively Exploited (CVE-2025-2611) | Blog | VulnCheck

https://www.vulncheck.com/blog/ictbroadcast-kev
GitHub pull request

Add ICTBroadcast Unauthenticated Remote Code Execution (CVE-2025-2611)

Fix merged in rapid7/metasploit-framework PR #20446 on 2025-08-05 — awaiting tagged release

https://github.com/rapid7/metasploit-framework/pull/20446

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 61× 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 → 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 270 rows 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 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. The fix is not yet in a release, so defenders should restrict or isolate affected systems accordingly until it ships.

  • Metasploitexploit/linux/http/ictbroadcast_unauth_cookie✓ verified
    Published Aug 5, 2025

    ICTBroadcast Unauthenticated Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-2611.yaml
    Published Feb 11, 2026

    ICTBroadcast - Command Injection

    Open source ↗

Frequently asked(5)

What is CVE-2025-2611?
CVE-2025-2611 is a critical-severity vulnerability; its CVE record was published on August 5, 2025. The ICTBroadcast application unsafely passes session cookie data to shell processing, allowing an attacker to inject shell commands into a session cookie that get executed on the server. This results in unauthenticated remote code execution in the session handling. Versions 7.4 and below are known…
When was the CVE record for CVE-2025-2611 published?
The CVE record for CVE-2025-2611 was published on August 5, 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 November 8, 2026; the record at its source may have been updated since.
Is CVE-2025-2611 actively exploited?
CVE-2025-2611 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 8.4% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-2611?
CVE-2025-2611 has a CVSS base score of 9.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2025-2611?
An upstream fix for CVE-2025-2611 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-2611?

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