CVE-2026-54026: LibreChat: Cross-User Message Injection via Parameter Confusion

Published Nov 20, 2026
·
Updated

LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.6, POST /api/messages/:conversationId authorizes req.params.conversationId in api/server/middleware/validateMessageReq.js but persists attacker-controlled req.body.conversationId through api/server/routes/messages.js. An authenticated attacker can use an owned conversation in the URL while naming a victim conversation in the body, causing an attacker-controlled message to be stored in the victim conversation. This issue is fixed in version 0.8.6.

Affected Software

1 affected component
librechat librechat<0.8.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.8.6

Event History

Nov 20, 2026
CVE Published
via MITRE·08:17 PM
Data Sourced
via MITRE·08:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any authenticated LibreChat user can exploit it, provided they have an existing conversation they own to supply in the request URL. The attacker does not need to interact with another user.

2

Which deployments are affected?

LibreChat versions before 0.8.6 are affected. The vulnerable endpoint is POST /api/messages/:conversationId.

3

What is the impact of successful exploitation?

An attacker can cause an attacker-controlled message to be stored in another user's conversation. The provided severity vector indicates integrity impact, with no stated confidentiality or availability impact.

4

How can administrators determine whether an instance may have been affected?

Review messages in user conversations for content that does not match the conversation owner's activity, particularly where the message may have been submitted through POST /api/messages/:conversationId using a different conversation ID in the request body. The available information does not provide a specific log signature or detection method.

5

What should be done if the instance is running a vulnerable version?

Upgrade LibreChat to version 0.8.6, which fixes the issue. No alternative mitigation is specified in the provided information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203