VulnerabilityPublished 27 Oct 2026

CVE-2026-118172: The strapi/strapi (Core Admin / Webhook Runner) package is vulnerable to a semi-blind SSRF via a

Source GCVE Database

Authoritative record:CVE-2026-118172· Medium

Not known to be exploited.

Data as of 27 Oct 2026, 22:14 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-q3j4-m5fm-rj65

What to do

Affected software

Product	Affected	Fixed in
StrapiStrapi Open Source and Enterprise Headless CMS	Affected =5.51.0	Fixed in–
GitHubstrapi/strapi`pkg:github/strapi/strapi`Other threats	Affected =5.51.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, consider disabling or restricting webhook functionality or implementing network-level controls to prevent the server from making unauthorized outbound HTTP requests. Monitor vendor channels for official patches or updates.

Description

The strapi/strapi Core Admin / Webhook Runner component is vulnerable to a semi-blind Server-Side Request Forgery (SSRF) via webhook follow-redirect behavior. The webhook dispatcher follows HTTP redirects automatically without verifying the IP address after redirection or checking if the target is within private network ranges. Additionally, non-2xx HTTP responses from target endpoints are reflected back to the caller.

Impact

An attacker can leverage this SSRF vulnerability to make the server perform HTTP requests to internal or protected network resources that are normally inaccessible externally. This can lead to information disclosure or facilitate further attacks within the internal network. The reflection of non-2xx responses to the attacker provides feedback that can be used to confirm the presence and behavior of internal endpoints.

Summary

The vulnerability in strapi/strapi's Core Admin / Webhook Runner allows an attacker to exploit the webhook dispatcher's automatic HTTP redirect following. Because the dispatcher does not perform IP resolution after redirects or enforce RFC1918/link-local boundary checks, it can be tricked into making requests to internal or otherwise restricted network resources. The semi-blind SSRF nature means the attacker can infer some information from the reflected non-2xx responses, potentially aiding further attacks or reconnaissance.

References

Community reviews

Loading reviews…