Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-25521 high CVSS 8.8

Vulnerability in locutus (CVE-2026-25521)

Summary

Vulnerability in locutus (CVE-2026-25521). Successful exploitation can lead to full system takeover. Exploitable via locutus.php.strings.parse_str. Mitigation: upgrade to 2.0.39 or later.

Original description

The description as published by the source.

Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. In versions from 2.0.12 to before 2.0.39, a prototype pollution vulnerability exists in locutus. Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using String.prototype. This issue has been patched in version 2.0.39.

Source: NIST National Vulnerability Database 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-25521 has been found in locutus.
Attackers can target a specific entry point like locutus.php.strings.parse_str over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade locutus to 2.0.39 or later.
If unsure, ask your IT team or search "locutus CVE-2026-25521" on the vendor's site.

CVE-2026-25521 (locutus) — CWE-915 / CVSS v3 8.8
Attack vector: local / no user interaction
Attack surface: locutus.php.strings.parse_str
Patched: 2.0.39 — 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

A vulnerability (CWE-915) exists in locutus. Attackers reach the vulnerable code path via locutus.php.strings.parse_str.

📍 Affected scope

Check the vendor advisory for the affected versions of locutus. Attack surface: locutus.php.strings.parse_str.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.0.39.

🛡️ 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 'locutus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'locutus' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade locutus to 2.0.39

    ステージング環境で 2.0.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

npm locutus
[{"type":"SEMVER","events":[{"introduced":"2.0.12"},{"fixed":"2.0.39"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details