Vulnerability in langroid (CVE-2026-54771)
Summary
Vulnerability in langroid (CVE-2026-54771). Confidential information can be exposed externally. Exploitable via Entity.USER. Mitigation: upgrade to 0.65.3 or later.
Original description
The description as published by the source.
Langroid is a framework for building large-language-model-powered applications. Prior to version 0.65.3, a Langroid application exposing a chat interface to untrusted users may allow direct tool invocation via raw JSON payloads, even when tools are registered with use=False, handle=True. Version 0.65.3 fixes the issue.
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-54771 has been found in langroid.
Attackers can target a specific entry point like Entity.USER over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade langroid to 0.65.3 or later.
If unsure, ask your IT team or search "langroid CVE-2026-54771" on the vendor's site.
CVE-2026-54771 (langroid) — CWE-74 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Entity.USER / Entity.LLM / False
Patched: 0.65.3 — 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.
A vulnerability (CWE-74) exists in langroid. Attackers reach the vulnerable code path via Entity.USER.
Check the vendor advisory for the affected versions of langroid. Attack surface: Entity.USER / Entity.LLM / False.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.65.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langroid' . 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
-
1Identify exposure identify
grep -r 'langroid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langroidを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langroid to 0.65.3ステージング環境で 0.65.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com