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: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration

No KEV listing collectedCVSS not publishedFix not stated

Assessment

Severity
Important
CVSS base score
Not published
Impact
Not stated
Exploitation detected
Unknown: not stated by MSRC
Exploitability
Not assessed
Publicly disclosed
Unknown: not stated by MSRC
EPSS · 30-day forecast
No EPSS score collected
Customer action
Required: follow the MSRC remediation guidance
More details
Public detection template
No Nuclei template is listed in the current collected catalog
Component
Mariner
Weakness
CWE-195: Signed to Unsigned Conversion Error
Issued by
GitHub_M
Published
19 Sep 2026 · September 2026
Last revised
21 Nov 2026Information published.

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software
5 affected products
  • azl3 keda 2.14.1-18 on Azure Linux 3.0
  • azl3 keda 2.14.1-19 on Azure Linux 3.0
  • azl3 telegraf 1.31.0-31 on Azure Linux 3.0
  • azl3 telegraf 1.31.0-33 on Azure Linux 3.0
  • azl4 telegraf 1.38.2-5.azl4 on Azure Linux 4.0

What changed

  1. Affected products: azl3 keda 2.14.1-18 on Azure Linux 3.0, azl3 keda 2.14.1-19 on Azure Linux 3.0, azl3 telegraf 1.31.0-31 on Azure Linux 3.0, azl3 telegraf 1.31.0-33 on Azure Linux 3.0 → azl3 keda 2.14.1-18 on Azure Linux 3.0, azl3 keda 2.14.1-19 on Azure Linux 3.0, azl3 telegraf 1.31.0-31 on Azure Linux 3.0, azl3 telegraf 1.31.0-33 on Azure Linux 3.0, azl4 telegraf 1.38.2-5.azl4 on Azure Linux 4.0
  2. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  3. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  4. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  5. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  6. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  7. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  8. Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
  9. Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  10. Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (46)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 21 Nov 2026 · 08:49:25 UTC Last revised16 Nov 2026 23:13 UTC → 21 Nov 2026 01:15 UTC
  2. 21 Nov 2026 · 08:49:25 UTC Affected productsazl3 keda 2.14.1-18 on Azure Linux 3.0, azl3 keda 2.14.1-19 on Azure Linux 3.0, azl3 telegraf 1.31.0-31 on Azure Linux 3.0, azl3 telegraf 1.31.0-33 on Azure Linux 3.0 → azl3 keda 2.14.1-18 on Azure Linux 3.0, azl3 keda 2.14.1-19 on Azure Linux 3.0, azl3 telegraf 1.31.0-31 on Azure Linux 3.0, azl3 telegraf 1.31.0-33 on Azure Linux 3.0, azl4 telegraf 1.38.2-5.azl4 on Azure Linux 4.0
  3. 17 Nov 2026 · 09:10:20 UTC Last revised13 Oct 2026 01:48 UTC → 16 Nov 2026 23:13 UTC
  4. 13 Nov 2026 · 12:10:20 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  5. 13 Nov 2026 · 12:10:20 UTC Source coverage: public-exploit-codeIncomplete → Current
  6. 13 Nov 2026 · 12:10:20 UTC Source coverage: first-epssIncomplete → Current
  7. 13 Nov 2026 · 12:10:20 UTC Source coverage: msrc-cvrfIncomplete → Current
  8. 13 Nov 2026 · 11:07:20 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  9. 13 Nov 2026 · 11:07:20 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  10. 13 Nov 2026 · 11:07:20 UTC Source coverage: first-epssCurrent → Incomplete
  11. 13 Nov 2026 · 11:07:20 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  12. 6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  13. 6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
  14. 6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
  15. 6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
  16. 6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  17. 6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  18. 6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
  19. 6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  20. 2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  21. 2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
  22. 2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
  23. 2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
  24. 2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  25. 2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  26. 2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
  27. 2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  28. 29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
  29. 29 Oct 2026 · 20:19:26 UTC EPSSNot scored → No EPSS score collected
  30. 29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
  31. 29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → Unknown: not stated by MSRC
  32. 29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → Unknown: not stated by MSRC
  33. 23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
  34. 23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  35. 23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
  36. 23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
  37. 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
  38. 23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
  39. 23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
  40. 23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
  41. 23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  42. 23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
  43. 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
  44. 23 Oct 2026 · 08:31:50 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  45. 18 Oct 2026 · 14:54:30 UTC Link: September 2026/security?release=2026-Sep#cves
  46. 14 Oct 2026 · 11:22:42 UTC Source coverage: msrc-cvrfIncomplete → Current

Explore global source statements, affected packages and advisory history for CVE-2026-77406. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

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-77406

Published

RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. This issue is fixed in version 1.13.0.

Source published
16 Sep 2026 14:37:36 UTC
Source modified
16 Sep 2026 18:35:40 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.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

euvd · EUVD-2026-80808

Published

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQ…

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. 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:37:36 PM

dateUpdated: Sep 16, 2026, 6:35:40 PM

10 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: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: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

msrc_CVE-2026-77406: RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration

CVE-2026-77406

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

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: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: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: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

Source published
Sep 16, 2026, 2:37:36 PM (timezone not stated)
Source modified
Sep 16, 2026, 6:35:40 PM (timezone not stated)
Saved here
21 Nov 2026 19:21:06 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.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

nvd · CVE-2026-77406

Published

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQ…

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. 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-195

Original publisher date fields

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

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

Source published
16 Sep 2026 15:17:49 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.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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-rm6m-hrcw-jw33

Published

RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration

## Summary A logic and resource exhaustion vulnerability exists in the AMQP client's Quality of Service (`Qos`) configuration method. The `Qos` function accepts signed integers (`int`) for the `prefetchCount` and `prefetchSize` parameters but casts them directly to unsigned integers (`uint16` and `uint32`, respectively) when formatting the wire-level frame. If a developer passes a negative integer (such as `-1`) to these parameters—frequently intended as a sentinel value meaning "no change" or "no limit"—the application performs an implicit signed-to-unsigned conversion. This wraps the values to their absolute maximum limit ($65535$ and $4294967295$). Consequently, a consumer expecting restricted message delivery rates is suddenly flooded with an unlimited volume of messages, potentially exhausting memory resources and crashing the application. --- ## Vulnerability Details ### Mechanism The bug manifests during the structural assignment inside the channel's `Qos` method: ```go // channel.go:795-796 PrefetchCount: uint16(prefetchCount), // -1 wraps to 65535 PrefetchSize: uint32(prefetchSize), // -1 wraps to 4294967295 ``` In Go, converting a negative signed integer to an unsigned integer shifts the value via two's complement arithmetic. Because no boundary validation or signedness check occurs prior to the cast: * Passing `-1` for `prefetchCount` yields a wire value of `65535`. * Passing `-1` for `prefetchSize` yields a wire value of `4294967295`. ### Impact The AMQP broker interprets a `prefetch-count` of `65535` as an instruction to dispatch messages to the consumer with virtually no concurrency limits. If the application is processing heavy payloads or relies on strict rate-limiting to maintain stability, this unexpected flood will cause rapid heap memory growth, unmanageable processing queues, and an eventual Out-Of-Memory (OOM) termination. --- ## Attack Vector An attacker who can manipulate configuration files, environmental variables, or API inputs that dictate client Qos settings can trigger an application-layer Denial of Service: 1. **Malicious Input:** An attacker sets a service's prefetch configuration parameter to `-1`. 2. **Implicit Overflow:** The application initializes the channel, executes `Qos(-1, ...)`, and transmits an unintended maximum-capacity request to the RabbitMQ/AMQP broker. 3. **Consumer Exhaustion:** The broker flushes the entire contents of the queue directly into the client consumer's network buffer, bypassing expected application concurrency barriers and inducing a crash.

Source published
17 Sep 2026 17:04:05 UTC
Source modified
1 Oct 2026 20:56:09 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:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

Publisher rating · HIGH

osv · GO-2026-6502

Published

RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration in github.com/rabbitmq/amqp091-go

RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration 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 21 Nov 23:38 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current