Skip to main content

Tag: NATS

Problems related to NATS, such as authorization failures, message loss, or configuration issues

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0045
Medium
Impact: 4/10
Mitigation: 4/10
NATS Authorization Failure Detected
The NATS server has emitted an Authorization Violation log entry, meaning a client attempted to connect, publish, subscribe, or perform another operation for which it lacks permission. Intermittent violations often point to misconfiguration or start-up chaos. However, sustained or widespread violations can signal credential expiry or missing secrets.
Authorization ProblemsnatsNATSSecurityAuthorizationPublic
CRE-2025-0046
Medium
Impact: 4/10
Mitigation: 4/10
NATS Permissions Violation Detected
The NATS server has emitted an Permission Violation log entry, meaninga client attempted to publish or subscribe to a subject for which it lackspermission.
Authorization ProblemsnatsNATSSecurityAuthorizationPublic
CRE-2025-0049
Low
Impact: 2/10
Mitigation: 8/10
NATS Payload Size Too Big
The NATS server is configured to publish messages with payloads that mayexceed the recommended maximum of 8 MB (the server’s default hard limitis 1 MB but it can be raised to 64 MB). Large messages put disproportionate pressure on broker memory, network buffers, and client back-pressure mechanisms.This warning signals NATS is at risk of degraded throughput, slowconsumers, and forced connection closures intended to protect clusterstability.
Message Queue ProblemsnatsNATSPublic
CRE-2025-0082
High
Impact: 0/10
Mitigation: 8/10
NATS JetStream HA failures: monitor goroutine, consumer stalls and unsynced replicas
Detects high-availability failures in NATS JetStream clusters due to:
  • Monitor goroutine failure — after node restarts, Raft group fails to elect a leader
  • Consumer deadlock — using DeliverPolicy=LastPerSubject + AckPolicy=Explicit with low MaxAckPending
  • Unsynced replicas — object store replication appears healthy but data is lost or inconsistent between nodes

These issues lead to invisible data loss, stalled consumers, or stream unavailability.
Message Queue ProblemsnatsNATSJetStreamRaftAck DeadlockUnsynced Replica
CRE-2025-0088
High
Impact: 9/10
Mitigation: 8/10
NATS JetStream Storage Exhaustion Detection
Detects NATS JetStream storage exhaustion conditions when streams reach configuredstorage limits (maximum bytes, maximum messages) causing message storage failures.These patterns indicate insufficient stream storage capacity relative to messageproduction rate, leading to message rejection and potential data loss.
Message Queue ProblemsjetstreamNATSJetStreamStorage ExhaustionMessage Storage FailureCapacity ExceededData Loss Risk
CRE-2025-0095
High
Impact: 9/10
Mitigation: 7/10
NATS Connection Exhaustion: Maximum Connections Exceeded
Detects NATS server connection exhaustion where the configured maximumconnection limit is exceeded, preventing new clients from establishingconnections. This represents a critical messaging infrastructure failurethat can cause cascading outages across distributed systems.
Message Queue ProblemsnatsNATSConnection ExhaustionCritical Infrastructure
CRE-2025-0103
Medium
Impact: 8/10
Mitigation: 7/10
NATS Connection Failures and Network Partitions
Detects NATS connection failures and network partitions that can impact message delivery and system reliability.
Message Queue ProblemsnatsNATSConnectivity