CVE-2026-55177

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). 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 a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-90083 (ENISA EUVD) · GHSA-r95q-fp26-h3hc (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

CloudTAK is a browser-based Common Operating Picture and situational awareness tool compatible with TAK. Prior to version 13.10.0, every route in the ESRI helper family (api/routes/esri.ts) takes a fully attacker-controlled URL from the request (POST /api/esri body url, and the portal / server / layer query parameters on the GET /api/esri/* routes) and passes it into EsriBase / EsriProxyPortal / EsriProxyServer / EsriProxyLayer in api/lib/esri.ts, which fetch it with the bare fetch from @tak-ps/etl. No IP / DNS / hostname classification is applied at any point, so the destination is never validated against private, loopback, or link-local ranges. Any authenticated user (the routes only require Auth.is_auth(config, req, { anyResources: true }), i.e. any token, not an admin) can therefore make the CloudTAK server issue arbitrary outbound GET/POST requests to internal addresses such as the cloud instance-metadata service (169.254.169.254), loopback admin ports (127.0.0.1:), and other hosts reachable only from inside the deployment VPC. This is a full-read SSRF, not blind: on success the upstream JSON body is returned to the caller via res.json(...), and on failure the upstream error string is reflected verbatim as ESRI Server Error: . An attacker can read cloud metadata (and the temporary IAM credentials the instance role exposes), enumerate internal services, and exfiltrate their response bodies. The sniff() URL classifier provides no protection: it only pattern-matches the pathname (/rest, /arcgis/rest, /sharing/rest), so a URL like http://169.254.169.254/arcgis/rest or http://127.0.0.1:8500/rest passes sniff() and is fetched. This issue has been patched in version 13.10.0.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: 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
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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

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

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

July 17, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 30, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Authenticated full-read SSRF in CloudTAK /api/esri* routes — user-controlled URL fetched with no IP-classification guard (CWE-918) · Advisory · dfpc-coe/CloudTAK · GitHub

https://github.com/dfpc-coe/CloudTAK/security/advisories/GHSA-r95q-fp26-h3hc
GitHub release Patch Available

v13.10.0

Patch available: dfpc-coe/CloudTAK v13.10.0

https://github.com/dfpc-coe/CloudTAK/releases/tag/v13.10.0

Vendor Advisories for CVE-2026-55177(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@tak-ps/cloudtak—
  • every version up to 13.10.0: fixed in 13.10.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-25 14:19 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-22 11:55 UTCEG score recompute
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-20 09:45 UTCEG score recompute
  12. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-18 03:30 UTCEG score recompute
  15. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-12 15:41 UTCEG score recompute
  22. 2026-10-11 19:39 UTCEG score recompute
  23. 2026-10-11 16:54 UTCEG score recompute
  24. 2026-10-11 14:17 UTCEG score recompute
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 17 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-30 17:27 UTCEG score recompute
  12. 2026-09-30 16:32 UTCEG score recomputeFirst assessed: 7.6 HIGH
  13. 2026-09-30 16:31 UTCMITRE cvelistV5CVSS v3 → 7.6 · CVSS v4 → 7.6
  14. 2026-08-01 16:01 UTCEG score recompute
  15. 2026-07-26 11:18 UTCEG score recompute
  16. 2026-07-23 03:20 UTCEG score recompute
  17. 2026-07-17 22:00 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

npm:@tak-ps/cloudtak

Frequently asked(5)

What is CVE-2026-55177?
CVE-2026-55177 is a high-severity vulnerability; its CVE record was published on July 17, 2026. CloudTAK is a browser-based Common Operating Picture and situational awareness tool compatible with TAK. Prior to version 13.10.0, every route in the ESRI helper family (api/routes/esri.ts) takes a fully attacker-controlled URL from the request (POST /api/esri body url, and the portal / server /…
When was the CVE record for CVE-2026-55177 published?
The CVE record for CVE-2026-55177 was published on July 17, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-55177 actively exploited?
CVE-2026-55177 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-55177?
CVE-2026-55177 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55177?
A fix for CVE-2026-55177 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55177 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-55177

Explore →

Is Your Infrastructure Affected by CVE-2026-55177?

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

Book a Demo →Browse All CVEs