PayRange API is missing proper authorization on management endpoints, which allows verbose details of every device on the PayRange network to be publicly accessible, with or without an account.
CVE-2026-18965
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026CSAF/csaf_files/OT/white/2026/icsa-26-237-04.json at develop · cisagov/CSAF · GitHub
https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-04.jsonPayRange API | CISA
https://www.cisa.gov/news-events/ics-advisories/icsa-26-237-04Vendor Advisories for CVE-2026-18965(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 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:26 UTCGHSA enrichment
- 2026-08-29 09:04 UTCEG score recompute
- 2026-08-29 09:04 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 20:40 UTCEG score recompute
- 2026-08-28 20:40 UTCGHSA enrichment
- 2026-08-28 19:46 UTCEG score recompute
- 2026-08-28 19:46 UTCGHSA enrichment
- 2026-08-28 12:58 UTCEG score recompute
- 2026-08-28 12:58 UTCGHSA enrichment
- 2026-08-28 00:32 UTCEG score recompute
- 2026-08-27 23:23 UTCEG score recompute
- 2026-08-27 23:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-18965?
When was CVE-2026-18965 disclosed?
Is CVE-2026-18965 actively exploited?
What is the CVSS score of CVE-2026-18965?
How do I remediate CVE-2026-18965?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18965
Is Your Infrastructure Affected by CVE-2026-18965?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.