{"id":"EUVD-2026-15973","enisaUuid":"49376694-ee16-3de1-9730-9af921b9dc82","description":"NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The nats-server offers a `Nats-Request-Info:` message header, providing information about a request. This is supposed to provide enough information to allow for account/user identification, such that NATS clients could make their own decisions on how to trust a message, provided that they trust the nats-server as a broker. A leafnode connecting to a nats-server is not fully trusted unless the system account is bridged too. Thus identity claims should not have propagated unchecked. Prior to versions 2.11.15 and 2.12.6, NATS clients relying upon the Nats-Request-Info: header could be spoofed. This does not directly affect the nats-server itself, but the CVSS Confidentiality and Integrity scores are based upon what a hypothetical client might choose to do with this NATS header. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.","datePublished":"Mar 25, 2026, 7:50:03 PM","dateUpdated":"Mar 28, 2026, 1:42:55 AM","baseScore":6.4,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","references":"https://github.com/nats-io/nats-server/security/advisories/GHSA-55h8-8g96-x4hj\nhttps://advisories.nats.io/CVE/secnote-2026-08.txt\n","aliases":"CVE-2026-33246\nGHSA-55h8-8g96-x4hj\n","assigner":"GitHub_M","epss":0.15,"enisaIdProduct":[{"id":"75265763-0925-34c7-a63f-24ba596ff8c4","product":{"name":"nats-server","vendor":{"name":"nats-io"}},"product_version":"2.12.0-RC.1, \u003c 2.12.6"},{"id":"b53f8180-19d5-3585-ac53-c04af0422602","product":{"name":"nats-server","vendor":{"name":"nats-io"}},"product_version":"\u003c 2.11.15"}],"enisaIdVendor":[{"id":"31e61592-721f-37ff-a1b3-106a8d85a569","vendor":{"name":"nats-io"}}],"enisaIdVulnerability":[{"id":"003b58fa-b16a-3552-9aad-985beb25484b","vulnerability":{"id":"GHSA-55h8-8g96-x4hj","description":"NATS: Leafnode connections allow spoofing of Nats-Request-Info identity headers","datePublished":"Mar 24, 2026, 9:50:25 PM","dateUpdated":"Mar 27, 2026, 10:10:07 PM","baseScore":0.0,"references":"https://github.com/nats-io/nats-server/security/advisories/GHSA-55h8-8g96-x4hj\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-33246\nhttps://advisories.nats.io/CVE/secnote-2026-08.txt\nhttps://github.com/nats-io/nats-server\n","enisa_id":"EUVD-2026-15973\n","aliases":"GHSA-55h8-8g96-x4hj\nCVE-2026-33246\n","epss":0.0,"dataProcessed":"Nov 9, 2026, 3:46:27 PM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"e1575e24-8ccf-3f0c-93ac-7f857aabd6e5","vulnerability":{"id":"CVE-2026-33246","description":"NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. The nats-server offers a `Nats-Request-Info:` message header, providing information about a request. This is supposed to provide enough information to allow for account/user identification, such that NATS clients could make their own decisions on how to trust a message, provided that they trust the nats-server as a broker. A leafnode connecting to a nats-server is not fully trusted unless the system account is bridged too. Thus identity claims should not have propagated unchecked. Prior to versions 2.11.15 and 2.12.6, NATS clients relying upon the Nats-Request-Info: header could be spoofed. This does not directly affect the nats-server itself, but the CVSS Confidentiality and Integrity scores are based upon what a hypothetical client might choose to do with this NATS header. Versions 2.11.15 and 2.12.6 contain a fix. No known workarounds are available.","datePublished":"Mar 25, 2026, 7:50:03 PM","dateUpdated":"Mar 28, 2026, 1:42:55 AM","status":"PUBLISHED","baseScore":6.4,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","references":"https://github.com/nats-io/nats-server/security/advisories/GHSA-55h8-8g96-x4hj\nhttps://advisories.nats.io/CVE/secnote-2026-08.txt\n","enisa_id":"EUVD-2026-15973\n","assigner":"GitHub_M","epss":0.15,"dataProcessed":"Nov 11, 2026, 7:23:33 AM","vulnerabilityProduct":[{"id":"8b621009-b1c3-3e8a-9763-097fec522b25","product":{"name":"nats-server","vendor":{"name":"nats-io"}},"product_version":"\u003c 2.11.15"},{"id":"a443ff3f-b54f-37f7-afed-3bcf6cff1c86","product":{"name":"nats-server","vendor":{"name":"nats-io"}},"product_version":"2.12.0-RC.1, \u003c 2.12.6"}],"vulnerabilityVendor":[{"id":"c9d1f4db-383d-35f5-9c8e-f7f47c30efdf","vendor":{"name":"nats-io"}}]}}],"enisaIdAdvisory":[{"id":"a98f29d2-a7f8-382a-a30b-e20e22894bc8","advisory":{"id":"WID-SEC-W-2026-0858","description":"NATS Server: Mehrere Schwachstellen","summary":"Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in NATS Server ausnutzen, um Informationen offenzulegen oder zu manipulieren, einen Denial-of-Service zu verursachen und Sicherheitsmechanismen zu umgehen.","datePublished":"Mar 24, 2026, 11:00:00 PM","dateUpdated":"Jun 1, 2026, 10:00:00 PM","baseScore":0.0,"references":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-0858.json\nhttps://wid.cert-bund.de/portal/wid/securityadvisory?name\u003dWID-SEC-2026-0858\n","aliases":"CVE-2026-33215\nCVE-2026-33216\nCVE-2026-33217\nCVE-2026-33218\nCVE-2026-33219\nCVE-2026-33222\nCVE-2026-33223\nCVE-2026-33246\nCVE-2026-33247\nCVE-2026-33248\nCVE-2026-33249\n","source":{"id":8,"name":"csaf_certbund"},"advisoryProduct":[{"id":"488e3e6d-5bd9-320b-a0c7-b9d7aaafac19","product":{"name":"Red Hat Enterprise Linux","vendor":{"name":"Red Hat"}}},{"id":"644ea6c0-8924-33c0-a131-907868c9fc88","product":{"name":"NATS Server","vendor":{"name":"open source"}}},{"id":"87105a8e-125a-335d-9a83-0f5ac770e9b7","product":{"name":"2.12.6","vendor":{"name":"open source"}}},{"id":"babec1db-4e2e-3b82-af34-e25a667409af","product":{"name":"2.11.15","vendor":{"name":"open source"}}}]}}]}