CVE-2026-66773

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-11. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

A malicious or compromised OData service could disclose sensitive authentication information and inject untrusted data into the application, which may leads to a high impact on confidentiality and low impact on integrity and no impact on Availability.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/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 computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: github.
generic

SAP Security Notes & News

https://url.sap/sapsecuritypatchday
github Patch Available

Server-controlled `__next` URL is not checking cross-origin · Advisory · SAP/python-pyodata · GitHub

https://github.com/SAP/python-pyodata/security/advisories/GHSA-hc5j-q32w-c25v

Vendor Advisories for CVE-2026-66773(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 22× in last 7d / 34× 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.

  1. 2026-08-20 23:07 UTCEG score recompute
  2. 2026-08-20 23:07 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 00:48 UTCEG score recompute
  5. 2026-08-20 00:48 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 02:25 UTCEG score recompute
  8. 2026-08-19 02:25 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 04:03 UTCEG score recompute
  11. 2026-08-18 04:03 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 05:44 UTCEG score recompute
  14. 2026-08-17 05:44 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 07:12 UTCEG score recompute
  17. 2026-08-16 07:11 UTCGHSA enrichment
  18. 2026-08-15 08:52 UTCEG score recompute
  19. 2026-08-15 08:52 UTCGHSA enrichment
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 10:32 UTCEG score recompute
  22. 2026-08-14 10:32 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 12:13 UTCGHSA enrichment
  25. 2026-08-12 13:54 UTCEG score recompute
Show 9 more
  1. 2026-08-12 13:54 UTCGHSA enrichment
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 15:35 UTCEG score recompute
  4. 2026-08-11 15:35 UTCGHSA enrichment
  5. 2026-08-11 14:33 UTCEG score recompute
  6. 2026-08-11 14:33 UTCGHSA enrichment
  7. 2026-08-11 01:21 UTCEG score recompute
  8. 2026-08-11 00:33 UTCEG score recompute
  9. 2026-08-11 00:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66773?
CVE-2026-66773 is a medium vulnerability published on August 11, 2026. A malicious or compromised OData service could disclose sensitive authentication information and inject untrusted data into the application, which may leads to a high impact on confidentiality and low impact on integrity and no impact on Availability.
When was CVE-2026-66773 disclosed?
CVE-2026-66773 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66773 actively exploited?
CVE-2026-66773 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.5% of all scored CVEs.
What is the CVSS score of CVE-2026-66773?
CVE-2026-66773 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-66773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66773, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66773?

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

Start Free Scan →Browse All CVEs