CVE-2026-12797

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-06-21. 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.

A security flaw has been discovered in BerriAI litellm up to 1.82.5. Affected is the function async_pre_call_hook of the file enterprise/enterprise_hooks/banned_keywords.py of the component Completions Interface. The manipulation of the argument prompt results in incorrect authorization. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
33(Track)
EG Risk 33/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 21, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 21, 2026
No patch confirmed yet.
generic

Security Feature Bypass in BannedKeywords and AzureContentSafety Guardrails via call_type Mismatch on Async Endpoints · GitHub

https://gist.github.com/YLChen-007/078179224f07cc4e39e4f141a18c817a

Vendor Advisories for CVE-2026-12797(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 55× 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 18:37 UTCEG score recompute
  2. 2026-07-27 18:37 UTCGHSA enrichment
  3. 2026-07-27 14:13 UTCEPSS rescore
  4. 2026-07-26 16:21 UTCEG score recompute
  5. 2026-07-26 16:20 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:05 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:30 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 20:22 UTCGHSA enrichment
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 15:00 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 12:40 UTCGHSA enrichment
  24. 2026-07-13 22:30 UTCEPSS rescore
  25. 2026-07-13 10:23 UTCGHSA enrichment
Show 44 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 08:06 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 05:49 UTCGHSA enrichment
  6. 2026-07-10 03:32 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 01:13 UTCGHSA enrichment
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-07 22:55 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 20:38 UTCGHSA enrichment
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 18:22 UTCGHSA enrichment
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 16:00 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 13:42 UTCGHSA enrichment
  22. 2026-07-02 11:26 UTCGHSA enrichment
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 09:09 UTCGHSA enrichment
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 06:53 UTCGHSA enrichment
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-29 04:35 UTCGHSA enrichment
  30. 2026-06-28 14:07 UTCEPSS rescore
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-28 02:15 UTCGHSA enrichment
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-26 23:57 UTCGHSA enrichment
  36. 2026-06-25 21:40 UTCGHSA enrichment
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-24 19:21 UTCGHSA enrichment
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-23 21:32 UTCEPSS rescore
  41. 2026-06-23 15:43 UTCGHSA enrichment
  42. 2026-06-22 13:25 UTCGHSA enrichment
  43. 2026-06-21 11:09 UTCEG score recompute
  44. 2026-06-21 11:07 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12797?
CVE-2026-12797 is a medium vulnerability published on June 21, 2026. A security flaw has been discovered in BerriAI litellm up to 1.82.5. Affected is the function asyncprecallhook of the file enterprise/enterprisehooks/banned_keywords.py of the component Completions Interface. The manipulation of the argument prompt results in incorrect authorization. The attack may…
When was CVE-2026-12797 disclosed?
CVE-2026-12797 was first published in the National Vulnerability Database on June 21, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12797 actively exploited?
CVE-2026-12797 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 67.4% of all scored CVEs.
What is the CVSS score of CVE-2026-12797?
CVE-2026-12797 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-12797?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12797, 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-12797

Explore →

Is Your Infrastructure Affected by CVE-2026-12797?

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

Start Free Scan →Browse All CVEs