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.

AI summary snake-internal / snake-material-v2

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. CVSS score: ?/10. 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`` without authentication.

📍 Affected scope

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. Run `grep -r 'cc.tweaked:cc-tweaked-1.21-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

1
Identify exposure identify
```
grep -r 'cc.tweaked:cc-tweaked-1.21-core' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `cc.tweaked:cc-tweaked-1.21-core` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade cc.tweaked:cc-tweaked-1.21-core to 1.119.0
```
ステージング環境で 1.119.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。