websocket-driver: Resource limit bypass via message compression
### Impact If this library is used in tandem with the `permessage-deflate` extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size. This is because this limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. ### Patches The issue has been patched in version 0.8.1, by checking the length of messages after they are processed by incoming extensions. All users should upgrade to this version. ### Workarounds No known workarounds exist. ### Acknowledgements This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-54464
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 17:32 UTC · Revision 1
Source evidence
websocket-driver: Resource limit bypass via message compression
core-osv · Original sourcePublished 17 Jul 2026, 20:03 UTC
### Impact If this library is used in tandem with the `permessage-deflate` extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size. This is because this limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. ### Patches The issue has been patched in version 0.8.1, by checking the length of messages after they are processed by incoming extensions. All users should upgrade to this version. ### Workarounds No known workarounds exist. ### Acknowledgements This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.
osv:CVE-2026-54464
Complete source record
{
"id": "73b16ec4404a8ecbfaf358f0841e610cbe420f3fda098ee7ffd83dc66f41897f",
"url": "https://osv.dev/vulnerability/CVE-2026-54464",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "websocket-driver: Resource limit bypass via message compression",
"summary": "### Impact If this library is used in tandem with the `permessage-deflate` extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size. This is because this limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. ### Patches The issue has been patched in version 0.8.1, by checking the length of messages after they are processed by incoming extensions. All users should upgrade to this version. ### Workarounds No known workarounds exist. ### Acknowledgements This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.",
"evidence": "osv:CVE-2026-54464",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-54464",
"aliases": [
"CVE-2026-54464",
"GHSA-33ph-fccm-39pj"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/faye/websocket-driver-ruby",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "5cab908d5e72d40345751edbd4f1e1ef75d53d89"
},
{
"fixed": "fa8641724f10bf3273585f1dcf9041f540bbd036"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.8.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "fa8641724f10bf3273585f1dcf9041f540bbd036"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"0.8.0",
"0.7.7",
"0.7.6",
"0.7.5",
"0.7.4",
"0.7.3",
"0.7.2",
"0.7.1",
"0.7.0",
"0.6.5",
"0.6.4",
"0.6.3",
"0.6.2",
"0.6.1",
"0.6.0",
"0.5.4",
"0.5.3",
"0.5.2",
"0.5.1",
"0.5.0",
"0.4.0",
"0.3.5",
"0.3.4",
"0.3.3",
"0.3.2",
"0.3.1",
"0.3.0",
"0.2.3",
"0.2.2",
"0.2.1",
"0.2.0",
"0.1.0",
"0.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54464.json"
}
}
],
"modified": "2026-10-28T02:30:21.595684990Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54464.json",
"https://github.com/faye/websocket-driver-ruby/security/advisories/GHSA-33ph-fccm-39pj",
"https://nvd.nist.gov/vuln/detail/CVE-2026-54464",
"https://github.com/faye/websocket-driver-ruby/commit/fa8641724f10bf3273585f1dcf9041f540bbd036"
],
"provider_metadata": {
"cwe_ids": [
"CWE-770"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54464.json"
}
},
"related_cves": [
{
"value": "CVE-2026-54464",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 487847,
"published_at": "2026-07-17T20:03:36.326+00:00"
}