CVE-2026-44761

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

SAP Commerce Cloud could retain a sample OAuth2 client with publicly documented sample credentials originating from sample configuration provided in SAP Help Portal documentation. If left unchanged, an unauthenticated attacker could use these well-known credentials to obtain a valid access token and invoke certain APIs to read and modify data. Successful exploitation results in high impact on confidentiality and integrity, with no impact on availability.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-44761(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 18× in last 7d / 47× 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-07-27 09:41 UTCGHSA enrichment
  2. 2026-07-27 06:03 UTCGHSA enrichment
  3. 2026-07-27 02:22 UTCGHSA enrichment
  4. 2026-07-26 22:44 UTCGHSA enrichment
  5. 2026-07-26 19:06 UTCGHSA enrichment
  6. 2026-07-26 15:28 UTCEG score recompute
  7. 2026-07-26 15:28 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 11:50 UTCEG score recompute
  11. 2026-07-26 11:50 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-24 14:17 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 03:15 UTCEG score recompute
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:24 UTCEPSS rescore
  18. 2026-07-20 17:08 UTCEPSS rescore
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 02:29 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-17 05:12 UTCGHSA enrichment
  23. 2026-07-17 01:35 UTCGHSA enrichment
  24. 2026-07-16 21:56 UTCGHSA enrichment
  25. 2026-07-16 18:18 UTCGHSA enrichment
Show 22 more
  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 14:40 UTCGHSA enrichment
  3. 2026-07-16 11:03 UTCGHSA enrichment
  4. 2026-07-16 07:25 UTCGHSA enrichment
  5. 2026-07-16 03:48 UTCGHSA enrichment
  6. 2026-07-16 00:10 UTCGHSA enrichment
  7. 2026-07-15 20:33 UTCGHSA enrichment
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 16:55 UTCGHSA enrichment
  10. 2026-07-15 13:18 UTCGHSA enrichment
  11. 2026-07-15 09:40 UTCGHSA enrichment
  12. 2026-07-15 06:03 UTCGHSA enrichment
  13. 2026-07-15 02:23 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 22:44 UTCGHSA enrichment
  16. 2026-07-14 19:06 UTCGHSA enrichment
  17. 2026-07-14 15:27 UTCGHSA enrichment
  18. 2026-07-14 11:48 UTCGHSA enrichment
  19. 2026-07-14 08:09 UTCGHSA enrichment
  20. 2026-07-14 04:31 UTCGHSA enrichment
  21. 2026-07-14 00:54 UTCEG score recompute
  22. 2026-07-14 00:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-44761?
CVE-2026-44761 is a critical vulnerability published on July 14, 2026. SAP Commerce Cloud could retain a sample OAuth2 client with publicly documented sample credentials originating from sample configuration provided in SAP Help Portal documentation. If left unchanged, an unauthenticated attacker could use these well-known credentials to obtain a valid access token…
When was CVE-2026-44761 disclosed?
CVE-2026-44761 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44761 actively exploited?
CVE-2026-44761 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 62.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44761?
CVE-2026-44761 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44761?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44761, 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-44761

Explore →

Is Your Infrastructure Affected by CVE-2026-44761?

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