CVE-2026-47695 CC-Tweaked has an SSRF Protection Bypass with NAT64

High 7.1 Published Updated

Attackers can bypass SSRF protections in CC-Tweaked to access internal IPv4 services via NAT64 addresses on IPv6-capable servers.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-47695?

CVE-2026-47695 is a high-severity server-side request forgery vulnerability in CC-Tweaked, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

CC: Tweaked is a mod for Minecraft which adds programmable computers, turtles, and more to the game. Prior to version 1.119.0, CC-Tweaked's HTTP API (`http.request`, `http.websocket`) blocks requests to private network ranges to prevent server-side request forgery (SSRF). This protection can be bypassed on IPv6-capable servers using NAT64 well-known prefix addresses (`64:ff9b::/96`). An attacker who can execute Lua code can reach any internal IPv4 service that the filter is intended to block, by addressing it as `http://[64:ff9b::<ipv4-as-hex>]/` instead of its direct IPv4 address. This affects any CC-Tweaked deployment on a network with NAT64 routing — a configuration that is standard on AWS, GCP, and other cloud platforms when using IPv6-only subnets. Version 1.119.0 fixes the issue.

Weakness: CWE-918

Which versions are affected by CVE-2026-47695?

16 open source packages ship an affected version, including cc.tweaked:cc-tweaked-1.19.3-core, cc.tweaked:cc-tweaked-1.19.4-core and cc.tweaked:cc-tweaked-1.20-core.

PackageAffectedFixed in
cc.tweaked:cc-tweaked-1.19.3-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.19.3-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.19.4-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.19.4-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20-core MavenAll versions1.119.0
10 more packages
cc.tweaked:cc-tweaked-1.20.1-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.1-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.4-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.4-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.5-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.5-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.6-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.20.6-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.21-core MavenAll versions1.119.0
cc.tweaked:cc-tweaked-1.21-core MavenAll versions1.119.0

How do I fix CVE-2026-47695?

Upgrade cc.tweaked:cc-tweaked-1.19.3-core to 1.119.0 or later.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-47695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47695 exists.

Sources

Also known as GHSA-5jh9-2h63-pw4q.

Is CVE-2026-47695 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free