CC-Tweaked has an SSRF Protection Bypass with NAT64

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 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 · score source

EPSS

• CVE-2026-47695: 0.47% estimated exploitation activity in the next 30 days; percentile 40.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details The IP filter in PrivatePattern.matches() (AddressPredicate.java#L121–L130) blocks private network ranges by calling Java's standard InetAddress classification methods: When a NAT64 address such as 64:ff9b::c0a8:0101 (encoding 192.168.1.1) is resolved via new InetSocketAddress("64:ff9b::c0a8:0101", 80), Java returns an Inet6Address. Every method above…

Published by the source

29 May 2026, 20:21 UTC

Last modified by the source

29 May 2026, 20:21 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5jh9-2h63-pw4q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47695

Advisory: CC-Tweaked has an SSRF Protection Bypass with NAT64
IDs: CVE-2026-47695, GHSA-5jh9-2h63-pw4q
Record: https://patchnext.com/advisories/cve-2026-47695 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cc.tweaked:cc-tweaked-1.20.5-core 1.119.0; cc.tweaked:cc-tweaked-1.19.4-core 1.119.0; cc.tweaked:cc-tweaked-1.19.3-core 1.119.0; cc.tweaked:cc-tweaked-1.21-core 1.119.0; cc.tweaked:cc-tweaked-1.20.4-core 1.119.0; cc.tweaked:cc-tweaked-1.20.1-core 1.119.0; cc.tweaked:cc-tweaked-1.20-core 1.119.0; cc.tweaked:cc-tweaked-1.20.6-core 1.119.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven cc.tweaked:cc-tweaked-1.20.5-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.19.4-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.19.3-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.21-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.20.4-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.20.1-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.20-core: affected < 1.119.0; fixed in 1.119.0
- Maven cc.tweaked:cc-tweaked-1.20.6-core: affected < 1.119.0; fixed in 1.119.0

## Suggested inspection (read-only)
- Maven cc.tweaked:cc-tweaked-1.20.5-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.19.4-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.19.3-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.21-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.20.4-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.20.1-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.20-core: check the installed version with your package manager.
- Maven cc.tweaked:cc-tweaked-1.20.6-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cc.tweaked:cc-tweaked-1.20.5-core, cc.tweaked:cc-tweaked-1.19.4-core, cc.tweaked:cc-tweaked-1.19.3-core, cc.tweaked:cc-tweaked-1.21-core, cc.tweaked:cc-tweaked-1.20.4-core, cc.tweaked:cc-tweaked-1.20.1-core, cc.tweaked:cc-tweaked-1.20-core, cc.tweaked:cc-tweaked-1.20.6-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5jh9-2h63-pw4q (GitHub-reviewed advisory GHSA-5jh9-2h63-pw4q lists affected ranges: Maven cc.tweaked:cc-tweaked-1.21-core >=0 =0 =0 =0 =0 =0 =0 =0 <1.119.0)

Commands are suggestions: review each one before running it.