56859 matches found
AZL-104925 CVE-2026-67419 affecting package rabbitmq-server 3.13.7-9
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
DEBIAN-CVE-2026-67419
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
CVE-2026-67419
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
UBUNTU-CVE-2026-67419
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
EUVD-2026-87243
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
CVE-2026-67419
Prior to version 4.3.5 , RabbitMQ is vulnerable to a flaw where an authenticated user can trigger combinatorial CPU work and memory pressure. By binding a queue to a topic exchange and publishing a message with consecutive # segments in a binding key, the attacker forces topic matchers to revisit...
CVE-2026-67419
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...
CVE-2026-89032 BerriAI LiteLLM < 1.101.0-rc.1 Tenant Isolation Bypass via Semantic Cache Layer
BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between getsemanticcachetenantscope and getmetadatavariablename. Attackers...
CVE-2026-89032 BerriAI LiteLLM < 1.101.0-rc.1 Tenant Isolation Bypass via Semantic Cache Layer
BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between getsemanticcachetenantscope and getmetadatavariablename. Attackers...
CVE-2026-89032
BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between getsemanticcachetenantscope and getmetadatavariablename. Attackers...
CVE-2026-89032
BerriAI LiteLLM versions prior to 1.101.0-rc.1 are vulnerable to a tenant isolation bypass within the semantic cache layer . The flaw is caused by a metadata key mismatch between the _get_semantic_cache_tenant_scope() and _get_metadata_variable_name() functions. An authenticated remote attacker w...
EUVD-2026-87147
BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between getsemanticcachetenantscope and getmetadatavariablename. Attackers...
CVE-2026-89032 BerriAI LiteLLM < 1.101.0-rc.1 Tenant Isolation Bypass via Semantic Cache Layer
BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between getsemanticcachetenantscope and getmetadatavariablename. Attackers...
CVE-2026-98005
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...
DEBIAN-CVE-2026-98005
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...
CVE-2026-98005 erofs: delimit inode_share cache key components
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...
CVE-2026-98005
The Linux kernel contains a vulnerability within the erofs file system regarding the encoding of inode_share cache keys . Previously, keys were encoded as fingerprint || domain_id, which created ambiguity as the fingerprint could be incorrectly parsed as part of a domain ID. The fix involves chan...
CVE-2026-98005 erofs: delimit inode_share cache key components
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...
EUVD-2026-86658
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...
CVE-2026-98005
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inodeshare cache key components Previously, inodeshare keys were encoded as follows: fingerprint || domainid It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won'...