CVE-2026-47695

SSRF (Server-Side Request Forgery) in cc.tweaked:cc-tweaked-1.21-core (CVE-2026-47695)

Summary

SSRF in cc.tweaked:cc-tweaked-1.21-core (CVE-2026-47695). Risk of unauthorized operations or information disclosure. Exploitable via http.request. Mitigation: upgrade to 1.119.0 or later.

Original description

The description as published by the source.

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::]/ 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:

public boolean matches(InetAddress socketAddress) {
    return socketAddress.isAnyLocalAddress()
        || socketAddress.isLoopbackAddress()
        || socketAddress.isLinkLocalAddress()
        || socketAddress.isSiteLocalAddress()
        || socketAddress.isMulticastAddress()
        || isUniqueLocalAddress(socketAddress)
        || isCarrierGradeNatAddress(socketAddress)
        || additionalAddresses.contains(socketAddress);
}

When a NAT64 address such as `64…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47695 has been found in cc.tweaked:cc-tweaked-1.21-core.
Attackers can target a specific entry point like http.request over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cc.tweaked:cc-tweaked-1.21-core to 1.119.0 or later.
If unsure, ask your IT team or search "cc.tweaked:cc-tweaked-1.21-core CVE-2026-47695" on the vendor's site.

CVE-2026-47695 (cc.tweaked:cc-tweaked-1.21-core) — CWE-918
Attack surface: http.request / http.websocket / InetAddress / Inet6Address
Patched: 1.119.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in cc.tweaked:cc-tweaked-1.21-core. Attackers reach the vulnerable code path via http.request.

📍 Affected scope

Check the vendor advisory for the affected versions of cc.tweaked:cc-tweaked-1.21-core. Attack surface: http.request / http.websocket / InetAddress / Inet6Address.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.119.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで cc.tweaked:cc-tweaked-1.21-core を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade cc.tweaked:cc-tweaked-1.21-core to 1.119.0
```
ステージング環境で 1.119.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。