CVE-2026-66770

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

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

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

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

Due to an SQL Injection vulnerability in SAP Social intelligence, an authenticated attacker could directly inject an SQL DDL (Data Definition Language) string into the underlying database without further authorization. Successful exploitation could allow the attacker to make malicious changes to the database structure, resulting in a low impact to the confidentiality, integrity, and availability of the system.

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

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

SAP Security Notes & News

https://url.sap/sapsecuritypatchday
generic
https://me.sap.com/notes/3766473

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-66770?
CVE-2026-66770 is a medium vulnerability published on August 11, 2026. Due to an SQL Injection vulnerability in SAP Social intelligence, an authenticated attacker could directly inject an SQL DDL (Data Definition Language) string into the underlying database without further authorization. Successful exploitation could allow the attacker to make malicious changes to…
When was CVE-2026-66770 disclosed?
CVE-2026-66770 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-66770 actively exploited?
CVE-2026-66770 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-66770?
CVE-2026-66770 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-66770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66770, 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-66770

Explore →

Is Your Infrastructure Affected by CVE-2026-66770?

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

Start Free Scan →Browse All CVEs