CVE-2026-111323

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

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

Score 5.3 from GitHub Security Advisory published 2026-10-16. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated
5.3EG
EchelonGraph verdictPlan mitigationRemediate 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.3%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists samugit83 RedAmon versions up to and including 7.0.1 as affected. No release containing a fix is confirmed on record.

RedAmon through 7.0.1 contains an unauthenticated server-side request forgery vulnerability in the agent POST /tradecraft/verify endpoint because validate_url checks only the initial hostname. Attackers can submit a public URL that redirects or DNS-rebinds to internal addresses like cloud metadata services, receiving fetched content through the model-generated summary.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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.
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 public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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.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; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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

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

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (6)

Auto-updated Oct 15, 2026
No fix on record yet.
Web page

RedAmon through 7.0.1 Unauthenticated SSRF via /tradecraft/verify Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/redamon-through-7.0.1-unauthenticated-ssrf-via-tradecraft-verify-endpoint
Web page

RedAmon agent `/tradecraft/verify` unauthenticated SSRF via unvalidated redirects and DNS rebinding, plus GitHub token exfiltration - HackMD

https://hackmd.io/@hieuPenguinnn/redamon-tradecraft-verify-unauth-ssrf
Web page

redamon/agentic/orchestrator_helpers/tradecraft_lookup.py at e1dfdff671b7e76d3a002eeba37b01d92cb949e1 · samugit83/redamon · GitHub

https://github.com/samugit83/redamon/blob/e1dfdff671b7e76d3a002eeba37b01d92cb949e1/agentic/orchestrator_helpers/tradecraft_lookup.py#L539
Web page

redamon/agentic/orchestrator_helpers/tradecraft_lookup.py at e1dfdff671b7e76d3a002eeba37b01d92cb949e1 · samugit83/redamon · GitHub

https://github.com/samugit83/redamon/blob/e1dfdff671b7e76d3a002eeba37b01d92cb949e1/agentic/orchestrator_helpers/tradecraft_lookup.py#L231
Web page

redamon/agentic/api.py at e1dfdff671b7e76d3a002eeba37b01d92cb949e1 · samugit83/redamon · GitHub

https://github.com/samugit83/redamon/blob/e1dfdff671b7e76d3a002eeba37b01d92cb949e1/agentic/api.py#L1688
Web page

GitHub - samugit83/redamon: Open-source, self-hosted AI penetration testing framework: maps your attack surface into a graph, autonomously exploits it from a Kali sandbox with human approval gates, and opens PRs that fix what it finds. MCP both ways: plug in any MCP server as a tool, or drive RedAmon from Claude Code or your own agent. · GitHub

https://github.com/samugit83/redamon

Vendor Advisories for CVE-2026-111323(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-18 05:05 UTCEG score recompute
  6. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-16 19:46 UTCEG score recompute
  8. 2026-10-16 19:45 UTCGHSA enrichmentGHSA-g3vp-47q6-cfx3 · GitHub CVSS 5.3
  9. 2026-10-16 18:36 UTCEG score recompute
  10. 2026-10-16 18:35 UTCGHSA enrichmentGHSA-g3vp-47q6-cfx3 · GitHub CVSS 5.3
  11. 2026-10-16 18:22 UTCEG score recompute
  12. 2026-10-16 18:22 UTCGHSA enrichmentGHSA-g3vp-47q6-cfx3 · GitHub CVSS 5.3
  13. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-10-15 23:22 UTCEG score recompute
  15. 2026-10-15 21:51 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  16. 2026-10-15 21:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-111323?
CVE-2026-111323 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. RedAmon through 7.0.1 contains an unauthenticated server-side request forgery vulnerability in the agent POST /tradecraft/verify endpoint because validate_url checks only the initial hostname. Attackers can submit a public URL that redirects or DNS-rebinds to internal addresses like cloud metadata…
When was CVE-2026-111323 made public?
CVE-2026-111323 was made public on October 15, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-111323 actively exploited?
CVE-2026-111323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111323?
CVE-2026-111323 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111323?
No fix for CVE-2026-111323 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists samugit83 RedAmon versions up to and including 7.0.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-111323 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-111323?

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