Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-27129: Cloud Metadata SSRF Protection Bypass via IPv6 Resolution

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: craftcms/cms (Packagist) 4.16.19, 4.16.17, 5.8.23.

Low priority for now. Upgrade to craftcms/cms (Packagist) 4.16.19, 4.16.17, 5.8.23 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, the SSRF validation in Craft CMS’s GraphQL Asset mutation uses `gethostbyname()`, which only resolves IPv4 addresses. When a hostname has only AAAA (IPv6) records, the function returns the hostname string itself, causing the blocklist comparison to always fail and completely bypassing SSRF protection. This is a bypass of the security fix for CVE-2025-68437. Exploitation requires GraphQL schema permissions for editing assets in the `<VolumeName>` volume and creating assets in the `<VolumeName>` volume. These permissions may be granted to authenticated users with appropriate GraphQL schema access and/or Public Schema (if misconfigured with write permissions). Versions 4.16.19 and 5.8.23 patch the issue.

MediumCVSS 5.7 · v4.0—No exploit Fix available
Published
Feb 23, 2026
Updated
Jun 17, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.7
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-27129

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
craftcmscraft cms

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • craftcms craft cms3.5.0 and later · before 4.16.19
  • craftcms craft cms5.0.1 and later · before 5.8.23
  • craftcms craft cms5.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • craftcms cms

    • >= 4.5.0-RC1, < 4.16.19, >= 5.0.0-RC1, < 5.8.23affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistcraftcms/cmsfrom 3.5.0 · before 4.16.194.16.19
Packagistcraftcms/cmsfrom 3.5.0 · before 4.16.174.16.17
Packagistcraftcms/cmsfrom 5.0.0-RC1 · before 5.8.235.8.23
Packagistcraftcms/cmsfrom 5.0.0-RC1 · before 5.8.215.8.21

Other highest-scoring records for the same primary product.

  • CVE-2025-32432Craft CMS Allows Remote Code ExecutionKEV
    100Now
  • CVE-2024-56145RCE when PHP `register_argc_argv` config setting is enabled in craftcms/cmsKEV
    96Now
  • CVE-2025-23209Potential RCE with a compromised security key in craft/cmsKEV
    68This week

Published before and after this one in the same product

  • ← EarlierCVE-2026-27127Feb 23, 2026 · Craft CMS has Cloud Metadata SSRF Protection Bypass via DNS Rebinding
    28Monitor
  • ← EarlierCVE-2026-27128Feb 23, 2026 · Craft CMS's race condition in Token Service potentially allows for token usage greater than the token limit
    27Monitor
  • Later →CVE-2026-28695Mar 4, 2026 · Craft affected by authenticated RCE via Twig SSTI - create() function + Symfony Process gadget
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:craftcms/cms4.16.17Package registry (OSV)
Packagist:craftcms/cms4.16.19Package registry (OSV)
Packagist:craftcms/cms5.8.21Package registry (OSV)
Packagist:craftcms/cms5.8.23Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-2549314 days apartCraft has a SSRF in GraphQL Asset Mutation via HTTP Redirect
    27Monitor
  • CVE-2026-2549414 days apartCraft has a SSRF in GraphQL Asset Mutation via Alternative IP Notation
    27Monitor
  • CVE-2026-2549214 days apartCraft has a save_images_Asset graphql mutation can be abused to exfiltrate AWS credentials of underlying host
    21Monitor
  • CVE-2025-6843749 days apartCraft CMS vulnerable to Server-Side Request Forgery (SSRF) via GraphQL Asset Upload Mutation
    20Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records