Server-Side Request Forgery (SSRF) vulnerability in Drupal OpenAI Provider allows Server Side Request Forgery. This issue affects OpenAI Provider versions: from 0.0.0 to 1.1.1, from 1.2.0 to 1.2.2.
CVE-2026-13233
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.3; sources differ by 5.8.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 9.1(medium)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (1)
Auto-updated Jul 13, 2026OpenAI Provider - Moderately critical - Server-side Request Forgery - SA-CONTRIB-2026-053 | Drupal.org
https://www.drupal.org/sa-contrib-2026-053Vendor Advisories for CVE-2026-13233(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist:https://packages.drupal.org/8(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| drupal/ai_provider_openai | — | 1.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 31× in last 7d / 56× 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-07-29 13:25 UTCGHSA enrichment
- 2026-07-29 09:24 UTCGHSA enrichment
- 2026-07-29 05:22 UTCGHSA enrichment
- 2026-07-29 01:21 UTCGHSA enrichment
- 2026-07-28 21:19 UTCGHSA enrichment
- 2026-07-28 17:13 UTCEG score recompute
- 2026-07-28 17:12 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 13:07 UTCGHSA enrichment
- 2026-07-28 09:02 UTCGHSA enrichment
- 2026-07-28 04:58 UTCGHSA enrichment
- 2026-07-28 00:54 UTCGHSA enrichment
- 2026-07-27 20:53 UTCGHSA enrichment
- 2026-07-27 16:45 UTCEG score recompute
- 2026-07-27 16:45 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:24 UTCGHSA enrichment
- 2026-07-27 08:22 UTCGHSA enrichment
- 2026-07-27 04:20 UTCGHSA enrichment
- 2026-07-27 00:16 UTCGHSA enrichment
- 2026-07-26 20:14 UTCGHSA enrichment
- 2026-07-26 16:12 UTCEG score recompute
- 2026-07-26 16:12 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
Show 31 moreShow fewer
- 2026-07-26 12:07 UTCEG score recompute
- 2026-07-26 12:06 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 06:35 UTCGHSA enrichment
- 2026-07-17 02:32 UTCGHSA enrichment
- 2026-07-16 22:30 UTCGHSA enrichment
- 2026-07-16 18:29 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 14:26 UTCGHSA enrichment
- 2026-07-16 10:25 UTCEG score recompute▲ 9.10
- 2026-07-16 10:25 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 18:27 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
- 2026-07-13 17:12 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-07-13 16:09 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-10 22:19 UTCNVD update
- 2026-07-10 21:53 UTCEG score recompute
- 2026-07-10 21:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-13233?
When was CVE-2026-13233 disclosed?
Is CVE-2026-13233 actively exploited?
What is the CVSS score of CVE-2026-13233?
How do I remediate CVE-2026-13233?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-13233
Is Your Infrastructure Affected by CVE-2026-13233?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.