GHSA-gjgq-w2m6-wr5q: Langroid: handle_message() executes user-supplied tool JSON without sender verification
Langroid versions prior to 0.65.3 contain a vulnerability where the handle_message() function executes user-supplied tool JSON without verifying the message sender. This allows untrusted users to directly invoke tools registered with use=False, handle=True, bypassing intended restrictions. The flaw arises because the tool dispatch path does not check if the message originated from a user or the language model. This can lead to unauthorized execution of sensitive tool handlers.
AI Analysis
Technical Summary
In Langroid versions before 0.65.3, the handle_message() function executes user-supplied JSON tool messages without verifying the sender entity. Tools registered with use=False, handle=True are intended not to be invoked by end users, but due to missing sender verification in the agent_response() → handle_message() → get_tool_messages() path, a user can send raw JSON to directly invoke such tools. This bypasses the intended restriction that only the language model should trigger these handlers. The vulnerability can lead to unauthorized execution of tool handlers that may perform sensitive operations such as file access or database queries.
Potential Impact
An attacker who can send chat messages to a vulnerable Langroid application can invoke tool handlers that were intended to be inaccessible to end users. Depending on the enabled tools, this may allow unauthorized file read/write operations, database query execution, or access to internal orchestration functions. This breaks the security assumption that tools registered with use=False are not invocable by users, potentially leading to data exposure or manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, developers should avoid exposing Langroid chat interfaces to untrusted users or disable tools registered with use=False, handle=True. Review and restrict tool registrations to ensure that untrusted user input cannot directly invoke sensitive handlers. Monitor vendor channels for an official fix.
GHSA-gjgq-w2m6-wr5q: Langroid: handle_message() executes user-supplied tool JSON without sender verification
Description
Langroid versions prior to 0.65.3 contain a vulnerability where the handle_message() function executes user-supplied tool JSON without verifying the message sender. This allows untrusted users to directly invoke tools registered with use=False, handle=True, bypassing intended restrictions. The flaw arises because the tool dispatch path does not check if the message originated from a user or the language model. This can lead to unauthorized execution of sensitive tool handlers.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Langroid versions before 0.65.3, the handle_message() function executes user-supplied JSON tool messages without verifying the sender entity. Tools registered with use=False, handle=True are intended not to be invoked by end users, but due to missing sender verification in the agent_response() → handle_message() → get_tool_messages() path, a user can send raw JSON to directly invoke such tools. This bypasses the intended restriction that only the language model should trigger these handlers. The vulnerability can lead to unauthorized execution of tool handlers that may perform sensitive operations such as file access or database queries.
Potential Impact
An attacker who can send chat messages to a vulnerable Langroid application can invoke tool handlers that were intended to be inaccessible to end users. Depending on the enabled tools, this may allow unauthorized file read/write operations, database query execution, or access to internal orchestration functions. This breaks the security assumption that tools registered with use=False are not invocable by users, potentially leading to data exposure or manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, developers should avoid exposing Langroid chat interfaces to untrusted users or disable tools registered with use=False, handle=True. Review and restrict tool registrations to ensure that untrusted user input cannot directly invoke sensitive handlers. Monitor vendor channels for an official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gjgq-w2m6-wr5q
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-54771"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a4c340527e9c797195f64b5
Added to database: 07/06/2026, 23:02:29 UTC
Last enriched: 07/06/2026, 23:14:16 UTC
Last updated: 07/07/2026, 00:20:28 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.