DEBIAN-CVE-2026-107386
- Source
- https://security-tracker.debian.org/tracker/CVE-2026-107386
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-107386.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2026-107386
- Upstream
- Published
- 2026-10-08T19:17:01Z
- Modified
- 2026-10-10T09:47:46Z
- Severity
-
- 6.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/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 CVSS Calculator
- Summary
- [none]
- Details
-
amqp091-go is a Go AMQP 0.9.1 client. From 1.13.0 until 1.14.0, the frame-size mitigation from the prior allocation advisory can be bypassed before connection.tune completes because Connection.maxFrameSize uses zero for both the not-yet-negotiated and negotiated-unlimited states. A malicious or compromised AMQP peer can send a short body-frame header with a large declared payload length, causing ReadFrame and the body-frame parser to allocate attacker-selected memory before the payload is received or the frame's protocol state is rejected. The condition is reachable through public Open even when Config.FrameSize is set to the protocol minimum and can cause severe memory pressure, out-of-memory termination, or loss of the client process before authentication completes. This issue is fixed in version 1.14.0.
- References
Affected packages
Debian:12 / golang-github-rabbitmq-amqp091-go
Package
- Name
- golang-github-rabbitmq-amqp091-go
- Purl
- pkg:deb/debian/golang-github-rabbitmq-amqp091-go?arch=source&distro=bookworm
Debian:13 / golang-github-rabbitmq-amqp091-go
Package
- Name
- golang-github-rabbitmq-amqp091-go
- Purl
- pkg:deb/debian/golang-github-rabbitmq-amqp091-go?arch=source&distro=trixie
Debian:14 / golang-github-rabbitmq-amqp091-go
Package
- Name
- golang-github-rabbitmq-amqp091-go
- Purl
- pkg:deb/debian/golang-github-rabbitmq-amqp091-go?arch=source&distro=forky