Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-77404

Published

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, URI.String in uri.go concatenates CertFile, KeyFile, CACertFile, and ServerName values directly into an AMQPS query string instead of encoding them as URL query parameters with url.Values. If an application accepts a TLS asset path containing ampersand or equals delimiters and later reparses the serialized URI with ParseURI, the embedded delimiters can create or overwrite connection options, including paths to TLS certificate, key, or CA files. This can corrupt connection configuration or select unintended local cryptographic assets. This issue is fixed in version 1.13.0.

Source published
16 Sep 2026 14:40:49 UTC
Source modified
16 Sep 2026 15:21:51 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 8.7 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L

euvd · EUVD-2026-80817

Published

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, URI.String in uri.go concatenates CertFile, KeyFile, CACertFile, and ServerName values directly into an AMQPS query string instead of encoding them as URL query parameters with url.Values. If an application accepts a TLS asset path containing ampersand or equals delimiters and later reparses the serialized URI with ParseURI, the embedded delimiters can create or overwrite connection options, including paths to TLS certificate, key, or CA files. This can corrupt connection configuration or select unintended local cryptographic assets. This issue is fixed in version 1.13.0.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 16, 2026, 2:40:49 PM

dateUpdated: Sep 16, 2026, 3:21:51 PM

9 related source bulletins · separate from aliases

RHSA-2026:79546: Red Hat Security Advisory: Red Hat Quay 3.12.23

CVE-2026-17106 · CVE-2026-49825 · CVE-2026-54770 · CVE-2026-59879 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-82417 · CVE-2026-87776 · CVE-2026-94603

RHSA-2026:99022: Red Hat Security Advisory: Red Hat Quay - 3.16.7

CVE-2026-49825 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-93749 · CVE-2026-94603 · CVE-2026-97687 · CVE-2026-97689 · CVE-2026-102267 · CVE-2026-102268 · CVE-2026-102272 · CVE-2026-102273 · CVE-2026-102994 · CVE-2026-102996 · CVE-2026-102997 · CVE-2026-102998 · CVE-2026-102999 · CVE-2026-103000 · CVE-2026-110642 · CVE-2026-110697 · CVE-2026-112390 · CVE-2026-118669 · CVE-2026-123710

RHSA-2026:99026: Red Hat Security Advisory: Red Hat Quay - 3.17.7

CVE-2026-32591 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-84375 · CVE-2026-93749 · CVE-2026-97687 · CVE-2026-97689 · CVE-2026-102267 · CVE-2026-102268 · CVE-2026-102272 · CVE-2026-102273 · CVE-2026-102996 · CVE-2026-102997 · CVE-2026-102999 · CVE-2026-103000 · CVE-2026-110642 · CVE-2026-110697 · CVE-2026-112390 · CVE-2026-118669 · CVE-2026-123710

RHSA-2026:99019: Red Hat Security Advisory: Red Hat Quay - 3.18.3

CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-84394 · CVE-2026-93749 · CVE-2026-94603 · CVE-2026-97687 · CVE-2026-97689 · CVE-2026-102267 · CVE-2026-102268 · CVE-2026-102272 · CVE-2026-102273 · CVE-2026-102996 · CVE-2026-102997 · CVE-2026-102999 · CVE-2026-103000 · CVE-2026-110642 · CVE-2026-110697 · CVE-2026-112390 · CVE-2026-114613 · CVE-2026-118669 · CVE-2026-119194 · CVE-2026-123710

RHSA-2026:99024: Red Hat Security Advisory: Red Hat Quay - 3.14.10

CVE-2026-49825 · CVE-2026-54770 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-82417 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-87776 · CVE-2026-90711 · CVE-2026-93749 · CVE-2026-94603 · CVE-2026-97687 · CVE-2026-97689 · CVE-2026-102267 · CVE-2026-102268 · CVE-2026-102272 · CVE-2026-102273 · CVE-2026-102994 · CVE-2026-102996 · CVE-2026-102997 · CVE-2026-102998 · CVE-2026-102999 · CVE-2026-103000 · CVE-2026-110697 · CVE-2026-112390 · CVE-2026-118669 · CVE-2026-123710

RHSA-2026:79366: Red Hat Security Advisory: Red Hat Quay 3.10.27

CVE-2026-49825 · CVE-2026-54770 · CVE-2026-59879 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-82417 · CVE-2026-87776

RHSA-2026:77656: Red Hat Security Advisory: Red Hat Quay 3.9.27

CVE-2026-17106 · CVE-2026-49825 · CVE-2026-54770 · CVE-2026-59879 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-82417 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-87776

RHSA-2026:99023: Red Hat Security Advisory: Red Hat Quay - 3.15.9

CVE-2026-15792 · CVE-2026-32283 · CVE-2026-33818 · CVE-2026-39822 · CVE-2026-42504 · CVE-2026-49825 · CVE-2026-54770 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59879 · CVE-2026-67213 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-79921 · CVE-2026-82417 · CVE-2026-84375 · CVE-2026-93749 · CVE-2026-94603 · CVE-2026-97687 · CVE-2026-97689 · CVE-2026-102267 · CVE-2026-102268 · CVE-2026-102272 · CVE-2026-102273 · CVE-2026-102994 · CVE-2026-102996 · CVE-2026-102997 · CVE-2026-102998 · CVE-2026-102999 · CVE-2026-103000 · CVE-2026-110697 · CVE-2026-112390 · CVE-2026-118669 · CVE-2026-123710

RHSA-2026:68290: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

CVE-2026-63209 · CVE-2026-77403 · CVE-2026-77404 · CVE-2026-77406 · CVE-2026-77407 · CVE-2026-77409 · CVE-2026-77410 · CVE-2026-77412 · CVE-2026-81872 · CVE-2026-93450

Source published
Sep 16, 2026, 2:40:49 PM (timezone not stated)
Source modified
Sep 16, 2026, 3:21:51 PM (timezone not stated)
Saved here
15 Nov 2026 17:51:26 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 4.0 · 8.7 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L

nvd · CVE-2026-77404

Published

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, URI.String in uri.go concatenates CertFile, KeyFile, CACertFile, and ServerName values directly into an AMQPS query string instead of encoding them as URL query parameters with url.Values. If an application accepts a TLS asset path containing ampersand or equals delimiters and later reparses the serialized URI with ParseURI, the embedded delimiters can create or overwrite connection options, including paths to TLS certificate, key, or CA files. This can corrupt connection configuration or select unintended local cryptographic assets. This issue is fixed in version 1.13.0.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-116

Original publisher date fields

published: 2026-09-16T15:17:47.067

lastModified: 2026-09-23T18:19:19.803

Source published
16 Sep 2026 15:17:47 UTC
Source modified
23 Sep 2026 18:19:19 UTC
Saved here
25 Oct 2026 16:19:04 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · [email protected] · Secondary · 8.7 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

osv · GHSA-465g-fh3v-9jw4

Published

## Summary A query parameter injection vulnerability exists in the AMQP client's connection URI formatting logic. When generating or parsing connection URIs, TLS-related filesystem paths (such as certificates or keys) are appended directly to the URI's query string using string concatenation rather than secure URL encoding via functions like `url.QueryEscape`. If an application handles a TLS file path containing special character delimiters (such as `&` or `=`), these characters are interpreted as parameter separators by the URI parser. If the resulting `URI.String()` output is subsequently re-parsed via `ParseURI`, the injected fields can silently overwrite or hijack critical configuration parameters, forcing the client to use arbitrary connection settings or alternate TLS files. --- ## Vulnerability Details ### Mechanism The vulnerability lies within the lack of proper escaping when compiling connection string components into a raw URL format: ```go // Example of insecure string concatenation during URI building uri := fmt.Sprintf("amqps://user:pass@host/%s?certfile=%s&keyfile=%s", vhost, certPath, keyPath) ``` Because `certPath` and `keyPath` are not passed through `url.QueryEscape`, special URL characters preserve their control meanings. For instance, if a user supply a certificate path named: `/tmp/cert=foo&keyfile=/evil/path` The generated string translates into: `...?certfile=/tmp/cert=foo&keyfile=/evil/path&keyfile=/original/path` When this string passes back through `ParseURI` (common in connection re-dial routines or configuration replication steps), standard URL parsing mechanics treat the string as multiple distinct parameters. Depending on map assignment order inside the parser, the injected keys take precedence over the original parameters. ### Impact By manipulating the file paths used for TLS assets, an attacker or compromised local sub-system can: * Inject arbitrary alternative options or override protocol settings. * Substitute or switch keyfiles, leading to connection failures or the parsing of unauthorized cryptographic assets. * Corrupt connection state variables, triggering application-layer failures during connection setup or recovery. --- ## Attack Vector An attacker who has partial control over directory naming conventions or environmental variables used to specify local infrastructure paths can execute a parameter injection attack: 1. **Path Creation:** An attacker sets up a path containing deliberate URL parameter delimiters (e.g., `/var/lib/certs/client.crt?cacertfile=/tmp/fake_ca.crt&`). 2. **String Generation:** The application serializes the active connection state or passes the paths down to an unescaped URI builder function. 3. **Configuration Hijack:** The URI string is generated with the injected parameter embedded into the query structure. When the client attempts to reuse or re-parse this connection string during a connection retry or worker spin-up, it parses the injected `cacertfile` parameter, loading a different, unverified Certificate Authority string.

Source published
17 Sep 2026 17:03:55 UTC
Source modified
1 Oct 2026 20:56:11 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V4 · CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L

Publisher rating · HIGH

osv · GO-2026-6493

Published

RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection in github.com/rabbitmq/amqp091-go

Source published
1 Oct 2026 20:23:56 UTC
Source modified
1 Oct 2026 20:45:11 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current