Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33248: CWE-287: Improper Authentication in nats-io nats-server

0
Medium
VulnerabilityCVE-2026-33248cvecve-2026-33248cwe-287cwe-295
Published: Wed Mar 25 2026 (03/25/2026, 20:18:28 UTC)
Source: CVE Database V5
Vendor/Project: nats-io
Product: nats-server

Description

NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate's Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/25/2026, 20:46:11 UTC

Technical Analysis

CVE-2026-33248 identifies an improper authentication vulnerability (CWE-287) in the nats-io nats-server, a high-performance messaging server used in cloud and edge native environments. The issue arises when mTLS is used for client authentication with the 'verify_and_map' feature enabled, which maps client identities from the Subject Distinguished Name (DN) in client certificates. The vulnerability is due to incorrect enforcement of certain Relative Distinguished Name (RDN) patterns within the Subject DN, allowing an attacker who possesses a valid client certificate issued by a trusted Certificate Authority (CA) to bypass authentication controls. This bypass occurs because the server fails to properly validate or map the DN components, potentially granting unauthorized access. However, exploitation requires the attacker to have a valid certificate from a trusted CA and to exploit highly specific and unlikely DN naming patterns, limiting the practical risk. The vulnerability affects nats-server versions prior to 2.11.15 and versions from 2.12.0-RC.1 up to but not including 2.12.6. The issue was addressed in versions 2.11.15 and 2.12.6 by correcting DN pattern enforcement. No public exploits have been reported. Administrators are advised to review their CA certificate issuance policies and update to patched versions to mitigate the risk.

Potential Impact

The potential impact of CVE-2026-33248 is moderate due to the authentication bypass allowing unauthorized clients to connect to the nats-server under certain conditions. This could lead to unauthorized access to messaging infrastructure, potentially exposing sensitive data or allowing message injection or interception. However, the requirement for a valid client certificate from a trusted CA and the need for specific DN patterns significantly reduce the likelihood of exploitation. Organizations relying on nats-server for critical messaging in cloud or edge environments could face confidentiality and integrity risks if exploited, but availability is not directly impacted. The vulnerability could be leveraged by attackers with insider access or compromised CA certificates, increasing risk in environments with complex certificate issuance policies. Overall, the impact is limited but should not be ignored in high-security deployments.

Mitigation Recommendations

To mitigate CVE-2026-33248, organizations should upgrade nats-server to versions 2.11.15 or 2.12.6 or later, where the vulnerability is fixed. In the interim, administrators should audit and tighten their CA certificate issuance policies to prevent issuance of certificates with DN patterns that could be exploited. Review and restrict the use of the 'verify_and_map' feature if possible, or implement additional validation layers on client certificates. Employ strict monitoring and logging of client authentication attempts to detect anomalous DN patterns or unexpected client identities. Consider using alternative authentication mechanisms or multi-factor authentication to reduce reliance on DN pattern mapping. Regularly review and update TLS configurations and certificate trust stores to minimize risks from compromised or misissued certificates. Finally, maintain awareness of any emerging exploit reports and apply patches promptly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-18T02:42:27.509Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c4460af4197a8e3b7facff

Added to database: 3/25/2026, 8:31:06 PM

Last enriched: 3/25/2026, 8:46:11 PM

Last updated: 3/26/2026, 5:26:21 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses