Autobahn Python
Approved changes feed: RSS · Atom
cpe:2.3:a:crossbario:autobahn-python:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Crossbario (134ff373-4b44-5999-a2d2-dadccd60dce6) |
|---|---|
| Product | Autobahn Python (6f863121-bc4a-528c-8a1a-0f30d94cfb33) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-116579 |
vulnerable | 2026-11-03 10:15:21.935345 |
Autobahn Python: permessage-brotli inflates a whole frame before maxMessagePayloadSize is checked (incomplete fix of GHSA-hxp9-w8x3-p566)
MEDIUM (5.9)
Autobahn Python is a WebSocket and WAMP implementation for Python that supports Twisted and asyncio. From 26.7.1 until 26.10.1, PerMessageBrotli.decompress_message_data in compress_brotli.py calls the Brotli decompressor without an output limit and checks maxMessagePayloadSize only after a complete frame has been inflated. An unauthenticated WebSocket client can send a small, highly compressed frame that allocates hundreds of MiB before rejection, causing memory-exhaustion denial of service on servers that enable the opt-in permessage-brotli feature through the compress extra. Deflate and bzip2 already enforce the remaining output budget and are outside this residual vulnerability. This issue is fixed in version 26.10.1.
Published: 2026-10-26T20:29:22.906Z
Updated: 2026-10-27T14:18:18.772Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-77528 |
vulnerable | 2026-10-13 12:28:29.236086 |
Autobahn Python permessage-deflate bypasses maxMessagePayloadSize after inflation
MEDIUM (5.3)
Autobahn Python is a WebSocket and WAMP implementation for Python that supports Twisted and asyncio. Prior to 26.7.1, WebSocket endpoints that accept permessage-deflate and rely on maxMessagePayloadSize enforce that limit against the compressed frame length before inflation but do not recheck the decompressed message size before delivery. A remote unauthenticated client can send a valid compressed frame below the configured wire-size limit that expands beyond the application message limit, causing oversized data to be allocated, joined, validated, and passed to application callbacks. This can create resource-exhaustion pressure, but the advisory does not establish confidentiality or integrity impact. This issue is fixed in version 26.7.1.
Published: 2026-09-18T19:42:18.767Z
Updated: 2026-09-19T14:11:38.071Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.