Most recent entries from all

BIT-nats-2022-24450

2026-10-03T09:52:34.716799+00:00

Affected: Bitnami: nats

NATS nats-server before 2.7.2 has Incorrect Access Control. Any authenticated user can obtain the privileges of the System account by misusing the "dynamically provisioned sandbox accounts" feature.

certfr-2026-avi-0199 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Certaines d'entre elles permettent à un attaq…

2026-10-03T09:52:34.716861+00:00

certfr-2026-avi-0199

EUVD-2026-14187

2026-10-03T09:52:34.716883+00:00

EUVD-2026-14187

fkie_cve-2022-24450

2026-10-03T09:52:34.716896+00:00

NATS nats-server before 2.7.2 has Incorrect Access Control. Any authenticated user can obtain the privileges of the System account by misusing the "dynamically provisioned sandbox accounts" feature.

GHSA-g6w6-r76c-28j7 — Incorrect Authorization in NATS nats-server

2026-10-03T09:52:34.716919+00:00

Affected: Go: github.com/nats-io/nats-server/v2, Go: github.com/nats-io/nats-streaming-server

(This advisory is canonically )

## Problem Description

NATS nats-server through 2022-02-04 has Incorrect Access Control, with unchecked ability for clients to authorize into any account, because of a coding error in a long-extant experimental feature.

A client crafting the initial protocol-level handshake could, with valid credentials for any account, specify a target account and switch into it immediately. This includes any other tenant, and includes the System account which controls nats-server core operations.

For deployments not using multi-tenancy through NATS Accounts, there is still a vulnerability: normal users are able to choose to be in the System account.

An experimental feature to provide dynamically provisioned sandbox accounts was designed to allow a server administrator to turn on an option to allow clients to dynamically request a brand new account inline at connection time. This feature went nowhere, but lived on in the code and was used by a number of tests; support was never added to any client libraries or to the documentation.

A bug in handling the feature meant that if someone did in fact have valid account credentials, then they could specify any other existing account and they would be assigned into that account.

Release 2.7.2 of nats-server removes the feature. Because of the lack of client support and absence from protocol documentation, we feel this is safe operationally as well as the saf…

gsd-2022-24450

2026-10-03T09:52:34.716962+00:00

gsd-2022-24450

RHSA-2022:0735 — Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.4.2 security updates and bug fixes

2026-10-03T09:52:34.716975+00:00

nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codes nodejs-json-schema: Prototype pollution vulnerability fastify-static: open redirect via an URL with double slash followed by a domain moby: `docker cp` allows unexpected chmod of host file moby: data directory contains subdirectories with insufficiently restricted permissions, which could lead to directory traversal golang.org/x/crypto: empty plaintext packet causes panic containerd: Unprivileged pod may bind mount any privileged regular file on disk minio: user privilege escalation in AddUser() admin API node-fetch: exposure of sensitive information to an unauthorized actor nats-server: misusing the "dynamically provisioned sandbox accounts" feature authenticated user can obtain the privileges of the System account

WID-SEC-W-2022-0235 — Red Hat Advanced Cluster Management: Mehrere Schwachstellen ermöglichen Privilegieneskalation

2026-10-03T09:52:34.717011+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Advanced Cluster Management ausnutzen, um seine Privilegien zu erhöhen.