CVE-2026-47695 json
CC-Tweaked has an SSRF Protection Bypass with NAT64
published 5mo ago modified 3mo ago also EUVD-2026-46424 , GHSA-5jh9-2h63-pw4q
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven cc.tweaked:cc-tweaked-1.21-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.20.1-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.20.4-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.20.5-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.20.6-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.19.3-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.19.4-core 1.119.0
- maven cc.tweaked:cc-tweaked-1.20-core 1.119.0
- cc.tweaked cc-tweaked-1.19.3-core 1.119.0
- tweaked cc-tweaked 1.119.0
- cc.tweaked cc-tweaked-1.19.4-core 1.119.0
- cc.tweaked cc-tweaked-1.20-core 1.119.0
- cc.tweaked cc-tweaked-1.20.1-core 1.119.0
- cc.tweaked cc-tweaked-1.20.4-core 1.119.0
- cc.tweaked cc-tweaked-1.20.5-core 1.119.0
- cc.tweaked cc-tweaked-1.20.6-core 1.119.0
- cc.tweaked cc-tweaked-1.21-core 1.119.0
Is CVE-2026-47695 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/cc-tweaked/CC-Tweaked/security/advisories/GHSA-5jh9-2h63-pw4q referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | cc.tweaked:cc-tweaked-1.21-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.20.1-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.20.4-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.20.5-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.20.6-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.19.3-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.19.4-core | <1.119.0 |
1.119.0 |
| maven | cc.tweaked:cc-tweaked-1.20-core | <1.119.0 |
1.119.0 |
Affected products
- cc-tweaked CC-Tweaked
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
Sources
- CVE List CVE-2026-47695
- GitHub Advisory GHSA-5jh9-2h63-pw4q
- NVD CVE-2026-47695
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.