{"answers":{"affected":"1 open source package ship an affected version, including nats. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-58252 in the wild and no public exploit code.","fix":"Upgrade nats to a fixed version for your release line: 2.11.16 or 2.12.7.","what":"CVE-2026-58252 is a medium-severity authentication bypass vulnerability in nats-io nats-server, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58252 and fix it if it is affected.\n\nWhat it is: CVE-2026-58252 is a medium-severity authentication bypass vulnerability in nats-io nats-server, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-58252 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nats (Bitnami): affected all versions; fixed in 2.11.16, 2.12.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58252/ (Markdown: https://insights.sbomify.com/CVE-2026-58252/index.md)","id":"CVE-2026-58252","markdown":"https://insights.sbomify.com/CVE-2026-58252/index.md","name":"CVE-2026-58252","record":{"aliases":["AZL-92253","BIT-nats-2026-58252","DEBIAN-CVE-2026-58252","GHSA-wh7g-5m82-pmhr","JLSEC-2026-1152","MINI-q3w6-jpxw-hgc4","MINI-vhpc-p2rg-hhwp","UBUNTU-CVE-2026-58252"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NATS messaging server","requires_auth":"low_privilege","summary":"Authenticated users can bypass subject authorization rules via wildcard overlaps to read restricted messages in NATS Server.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nats-server","vendor":"linuxfoundation"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"NATS Server is a high-performance server for NATS.io, the cloud and edge native messaging system. Prior to 2.14.0, 2.12.7, and 2.11.16, an authenticated user could receive messages on denied subjects when a wildcard subscription overlapped with a configured wildcard deny rule but was not a subset of it, and queue subscriptions could also affect delivery to legitimate queue consumers. This issue is fixed in versions 2.14.0, 2.12.7, and 2.11.16.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NATS Server: Subscribe Authz Bypass via Wildcard-Overlap","id":"CVE-2026-58252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":1,"n_references":7,"next":{"headline":"NATS Server: Route API Auth Bypass","id":"CVE-2026-58253"},"packages":[{"ecosystem":"Bitnami","fixed":["2.11.16","2.12.7"],"introduced":["0","2.12.0"],"last_affected":[],"package":"nats","purl":"pkg:bitnami/nats","source":"BIT-nats-2026-58252"}],"prev":{"headline":"NATS Server: Queue Subscribe Authz Bypass","id":"CVE-2026-58251"},"products":["nats-server"],"published":"2026-07-08","related":[{"cvss_score":9.8,"headline":"NATS nats-server allows directory traversal via unintended path to a management action","id":"CVE-2022-28357","kev_date_added":null,"published":"2023-09-19"},{"cvss_score":8.8,"headline":"NATS Server: Route API Auth Bypass","id":"CVE-2026-58253","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":8.8,"headline":"Incorrect Authorization in NATS nats-server","id":"CVE-2022-24450","kev_date_added":null,"published":"2022-02-08"},{"cvss_score":8.6,"headline":"NATS has MQTT plaintext password disclosure","id":"CVE-2026-33216","kev_date_added":null,"published":"2026-03-25"},{"cvss_score":7.7,"headline":"NATS Server: Remote crash via integer overflow in Connz pagination","id":"CVE-2026-58207","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":7.5,"headline":"NATS Server: MQTT partial CONNECT packets can exhaust pre-auth memory","id":"CVE-2026-58210","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":7.5,"headline":"NATS Server: Pre-auth server crash via double INFO in leafnode handshake","id":"CVE-2026-58250","kev_date_added":null,"published":"2026-07-08"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["nats-io"]},"summary":"Authenticated users can bypass subject authorization rules via wildcard overlaps to read restricted messages in NATS Server.","url":"https://insights.sbomify.com/CVE-2026-58252/"}