← Back
CVE-2026-54546

SSRF (Server-Side Request Forgery) in @tak-ps/cloudtak (CVE-2026-54546)

Summary

SSRF in @tak-ps/cloudtak (CVE-2026-54546). Risk of unauthorized operations or information disclosure. Exploitable via `PUT /api/basemap`.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-54546** has been found in @tak-ps/cloudtak. Attackers can target a specific entry point like `PUT /api/basemap` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "@tak-ps/cloudtak CVE-2026-54546" on the vendor's site.
CVE-2026-54546 (@tak-ps/cloudtak) — CWE-918 / Attack surface: PUT /api/basemap / PUT /basemap / GET /latest/meta-data/iam/security-credentials/ / GET /decimal-ip-bypass 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 @tak-ps/cloudtak. Attackers reach the vulnerable code path via `PUT /api/basemap` without authentication.
📍 Affected scope
@tak-ps/cloudtak — . Attack surface: PUT /api/basemap / PUT /basemap / GET /latest/meta-data/iam/security-credentials/ / GET /decimal-ip-bypass.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `PUT /api/basemap` requests with malformed payloads or SQL meta-characters. Run `grep -r '@tak-ps/cloudtak' .` 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. 1
    Identify exposure identify
    grep -r '@tak-ps/cloudtak' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@tak-ps/cloudtak` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect
    grep 'PUT /api/basemap' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `PUT /api/basemap` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 7
    Post-deployment verification verify
    Replay attack against PUT /api/basemap on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @tak-ps/cloudtak
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →