p PatchFirst

PatchFirst · Свежие уязвимости

Базы данных: уязвимости стека · Страница 7

За последние 30 дней в Базы данных опубликовано уязвимостей: 109; в каталоге KEV: 0.

Фильтры уязвимостей
Базы данных

Уязвимостей: 1413

  1. CVE-2026-66068

    Средний · CVSS 5.6EPSS 0,14%Есть исправление

    RabbitMQ: Shovel DEBUG log of full state exposes decrypted URIs

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, ?LOG_DEBUG("shutting down Shovel '~ts', ... Shovel state: ~tp", [Name, State]) formats the entire state map. The 'uris' field holds plaintext URIs after credentials_obfuscation:decrypt (called in rabbit_shovel_util:deobfuscated_uris/2). No format_status/1,2 callback exists in rabbit_shovel_worker to redact it. Triggered when an autodelete shovel (src-delete-after = N) completes. With DEBUG logging enabled, autodelete-shovel completion writes the full shovel state map , including decrypted amqp://user:password@host/ URIs , to the broker l

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  2. CVE-2026-67229

    Средний · CVSS 6.9EPSS 0,39%Есть исправление

    RabbitMQ: Admin-only atom exhaustion: atomize_keys on vhost metadata

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, add_vhost/2 calls rabbit_data_coercion:atomize_keys/1 (the unsafe variant using binary_to_atom) on the vhost metadata map. The 20 MB management body limit fits ~1M+ short keys. Admin-only. An administrator importing a crafted definitions file can crash the node in a single request: a vhosts entry with ~1M unique metadata keys exhausts the atom table during import. Preconditions include administrator tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  3. CVE-2026-66080

    Средний · CVSS 5.9EPSS 0,32%Есть исправление

    RabbitMQ: Super-stream partitions unbounded allocation

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.11, 4.2.6, and 4.3.0, validate_partitions only checks that the requested partition count is at least 1, with no upper bound. A large count such as lists:seq(0, 500000000) allocates roughly 8GB. Preconditions include The rabbitmq_stream_management plugin must be enabled. The caller needs the management tag and access to the target vhost.. This issue is fixed in versions 4.1.11, 4.2.6, and 4.3.0.

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  4. CVE-2026-67240

    Низкий · CVSS 2.3EPSS 0,33%Есть исправление

    RabbitMQ: ReDoS via AMQP 1.0 SQL filter LIKE wildcard

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, pattern_to_regex maps % -> .*? and _ -> ., then compiles ^...$ with only [unicode]; re:run is called with only [{capture, none}] - no explicit match_limit. A pattern like %_%_..._%X becomes ^.*?..*?.....*?.X$ with overlapping lazy quantifiers. The whole-expression cap is ?MAX_EXPRESSION_LENGTH=4096 chars / ?MAX_TOKENS=200; a LIKE string literal is one token, so ~2000 %_ pairs fit. SQL filters are accepted unconditionally at rabbit_amqp_session.erl:3264 (no feature flag). Evaluated per-message at rabbit_stream_queue.erl:1439. OTP's default 10M match_limit caps eac

    • Обновитесь до 4.3.2-1
    Опубликовано Обновлено
  5. CVE-2026-66072

    Средний · CVSS 6EPSS 0,47%Есть исправление

    RabbitMQ: Atom table exhaustion via stream `chunk_selector`

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, get_chunk_selector/1 calls binary_to_atom on the raw client-supplied <<"chunk_selector">> property from post-auth subscribe and resolve_offset_spec frames, with no whitelist and no existing guard. An authenticated stream client with read access to any stream can crash the broker node. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol user with read access to at least one stream. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

    • Обновитесь до 4.3.2-1
    Опубликовано Обновлено
  6. CVE-2026-66067

    Средний · CVSS 6EPSS 0,35%Есть исправление

    RabbitMQ: Stream protocol skips per vhost per user connection limits

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, The stream open handler calls only check_vhost_access; it omits the node/vhost/user connection-limit checks that rabbit_reader performs for AMQP. A developer %% FIXME comment at the cited line explicitly acknowledges the gap. No compensating enforcement exists in connection tracking or elsewhere in rabbitmq_stream. An authenticated tenant can fully bypass operator-configured per-user and per-vhost connection caps by connecting via port 5552 instead of 5672. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol credentials Operator rel

    • Обновитесь до 4.3.2-1
    Опубликовано Обновлено
  7. CVE-2026-66069

    Низкий · CVSS 2.3EPSS 0,4%Есть исправление

    RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.13, 4.2.7, and 4.3.0, is_authorized/2 uses is_authorized_monitor for all methods. DELETE resets rabbit_core_metrics:reset_auth_attempt_metrics(). Impact is cosmetic (counters only, no log erasure), but inconsistent with rabbit_mgmt_wm_reset.erl which requires admin for the analogous operation. A monitoring-tagged user can reset the per-node authentication-attempt counters via DELETE /api/auth/attempts/:node, erasing evidence of brute-force activity. The sibling endpoint wm_reset requires administrator. Preconditions include Management plugin enabled monitoring tag. This issue

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  8. CVE-2026-67404

    Критический · CVSS 9.2EPSS 0,2%Есть исправление

    RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, When no CA bundle is available, ssl_options/1 falls back to [{verify, verify_none}] with no warning. An attacker in a man-in-the-middle position can forge the JWKS response, which leads the broker to accept arbitrary JWTs. Preconditions include The OAuth2 plugin must be in use with no cacertfile configured and the OS CA bundle empty or unreadable (for example, in a minimal container), and the attacker must hold a network man-in-the-middle position.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

    • Обновитесь до 3.12.1-1ubuntu1.7
    • Обновитесь до 3.5.7-1ubuntu0.16.04.4+esm3
    • Обновитесь до 3.6.10-1ubuntu0.5+esm1
    • Обновитесь до 3.8.3-0ubuntu0.3+esm2
    • Обновитесь до 3.9.27-0ubuntu0.6
    • Обновитесь до 4.0.5-10ubuntu5.2
    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  9. CVE-2026-67220

    Средний · CVSS 6EPSS 0,31%Есть исправление

    RabbitMQ: JMS topic exchange erl_scan atom exhaustion

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Java JMS client compiles selectors client-side, but the server does not enforce this , a raw AMQP client can send arbitrary selector strings. An authenticated low-privilege AMQP user confined

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  10. CVE-2026-67224

    Низкий · CVSS 2.1EPSS 0,36%Есть исправление

    RabbitMQ: Admin path-traversal write via trace name

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The trace consumer constructs the output path as filename:join(TraceDir, Name ++ ".log") where Name comes from PUT /api/traces/:vhost/:name. No safe_relative_path / traversal check is applied on the write side, while the read side (rabbit_tracing_files.erl) does call rabbit_misc:safe_relative_path/1 , proving the omission is an oversight, not design. The .log suffix is forced and the endpoint requires administrator. A user with the administrator tag can write a .log-suffixed file to an arbitrary filesystem path writable by the rabbitmq u

    • Обновитесь до 4.3.2-1
    Опубликовано Обновлено
  11. CVE-2026-66077

    Высокий · CVSS 7.3EPSS 0,15%Есть исправление

    RabbitMQ: Stored XSS via TLS peer-certificate DN in management UI

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, The management UI uses EJS 1.0 in which <%= ... %> does NOT HTML-escape. connection.ejs:135 renders <%= connection.ssl_details.peer_cert_subject %> (and peer_cert_issuer) directly into the page. The same pattern appears in streamConnection.ejs:102,106,110. The values come from rabbit_ssl:peer_cert_subject/1 which formats the DN as a string without HTML escaping. The verifier corrected the original researcher's claim: this is reachable only when the listener is configured with verify_peer (so the certificate must be signed by a CA in the broker'

    • Обновитесь до 3.12.1-1ubuntu1.7
    • Обновитесь до 3.5.7-1ubuntu0.16.04.4+esm3
    • Обновитесь до 3.6.10-1ubuntu0.5+esm1
    • Обновитесь до 3.8.3-0ubuntu0.3+esm2
    • Обновитесь до 3.9.27-0ubuntu0.6
    • Обновитесь до 4.0.5-10ubuntu5.2
    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  12. CVE-2026-66079

    Высокий · CVSS 8.2EPSS 0,32%Есть исправление

    RabbitMQ: Pre-auth AMQP 1.0 array32 zero-width element DoS

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the fra

    • Обновитесь до 3.12.1-1ubuntu1.7
    • Обновитесь до 3.5.7-1ubuntu0.16.04.4+esm3
    • Обновитесь до 3.6.10-1ubuntu0.5+esm1
    • Обновитесь до 3.8.3-0ubuntu0.3+esm2
    • Обновитесь до 3.9.27-0ubuntu0.6
    • Обновитесь до 4.0.5-10ubuntu5.2
    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  13. CVE-2026-66070

    Высокий · CVSS 7.6EPSS 0,37%Есть исправление

    RabbitMQ: CORS * reflects Origin with Allow-Credentials

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.17, 4.0.22, 4.1.13, and 4.2.6, match_origin/1 returned the bare reflected Origin and allowed credentials even when the wildcard "" was configured, so the response echoed the attacker's origin together with Access-Control-Allow-Credentials. The affected code is rabbit_mgmt_cors.erl. When the management plugin is configured with a wildcard CORS origin (cors_allow_origins = ""), the handler reflects the request Origin back in Access-Control-Allow-Origin and also sends Access-Control-Allow-Credentials: true. A malicious web page that a signed-in administrator visits can then use

    • Обновитесь до 3.12.1-1ubuntu1.7
    • Обновитесь до 3.5.7-1ubuntu0.16.04.4+esm3
    • Обновитесь до 3.6.10-1ubuntu0.5+esm1
    • Обновитесь до 3.8.3-0ubuntu0.3+esm2
    • Обновитесь до 3.9.27-0ubuntu0.6
    • Обновитесь до 4.0.5-10ubuntu5.2
    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  14. CVE-2026-67238

    Высокий · CVSS 7.1EPSS 0,33%Есть исправление

    RabbitMQ: Atom-table exhaustion via reply-to queue name decoding

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, rabbit_pid_codec:decompose_from_binary/1 parses a caller-supplied ETF-encoded binary and calls binary_to_atom(Node, utf8) on the node-name field. It is reached from rabbit_volatile_queue:pid_from_name/2, which is invoked for any queue name / routing key beginning amq.rabbitmq.reply-to.. The CandidateNodes membership check happens after the atom is created, and the surrounding try/catch cannot reclaim atoms (they are never GC'd). binary_to_existing_atom is not used. Any authenticated AMQP client can crash the entire Erlang VM (all vhosts, all connections) with ~1M

    • Обновитесь до 3.12.1-1ubuntu1.7
    • Обновитесь до 3.5.7-1ubuntu0.16.04.4+esm3
    • Обновитесь до 3.6.10-1ubuntu0.5+esm1
    • Обновитесь до 3.8.3-0ubuntu0.3+esm2
    • Обновитесь до 3.9.27-0ubuntu0.6
    • Обновитесь до 4.0.5-10ubuntu5.2
    • Обновитесь до 4.3.2-1
    Опубликовано Обновлено
  15. CVE-2026-66076

    Низкий · CVSS 2.3EPSS 0,33%Есть исправление

    RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure

    RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, is_authorized/2 calls rabbit_mgmt_util:is_authorized/2, which checks only the management tag, instead of is_authorized_vhost/2. The /api/queues/quorum/:vhost/:queue/status handler reads the vhost from the path without checking that the user can access it. Any management-tagged user can therefore read Raft status, including leader, members, term, and commit index, for quorum queues in inaccessible vhosts, exposing cross-tenant queue names and cluster topology. The management plugin must be enabled and the attacker must have a management t

    • Обновитесь до 4.3.0-2
    Опубликовано Обновлено
  16. CVE-2026-86227

    Низкий · CVSS 2.3EPSS 0,52%Есть исправление

    valkey-io valkey kvstore.c kvstoreGetHashtable out-of-bounds

    A weakness has been identified in valkey-io valkey up to 9.0.5/9.1.1. This affects the function kvstoreGetHashtable of the file src/kvstore.c. This manipulation of the argument didx causes out-of-bounds read. It is possible to initiate the attack remotely. The attack is considered to have high complexity. It is indicated that the exploitability is difficult. The exploit has been made available to the public and could be used for attacks. Patch name: 4691888e7fab3df128f0bde5750c9fde2ae552fa. To fix this issue, it is recommended to deploy a patch. Exploitation requires cluster mode plus attacker-controlled dump.rdb at startup (data-dir write ac

    • Обновитесь до 9.1.2-1
    Опубликовано Обновлено
  17. CVE-2026-85522

    Средний · CVSS 6.9EPSS 0,86%Есть исправление

    valkey-io valkey Slot Migration cluster_migrateslots.c createSlotImportJob out-of-bounds

    A vulnerability was detected in valkey-io valkey up to 9.5.4/9.1.0. Affected by this vulnerability is the function createSlotImportJob of the file src/cluster_migrateslots.c of the component Slot Migration. The manipulation of the argument job_name results in out-of-bounds read. The attack can be executed remotely. The exploit is now public and may be used. Upgrading to version 9.0.5 and 9.1.1 addresses this issue. The patch is identified as f4dc3ca09eb650c2fe14060090a41c524eca803f. Upgrading the affected component is advised.

    • Обновитесь до 9.0.4-0ubuntu0.2
    • Обновитесь до 9.0.5
    • Обновитесь до 9.1.1
    • Обновитесь до 9.1.2-1
    Опубликовано Обновлено
  18. CVE-2026-82677

    Средний · CVSS 4.8EPSS 0,52%Есть исправление

    valkey-io valkey Module Timer module.c moduleTimerHandler double free

    A vulnerability was determined in valkey-io valkey 9.1.0. Impacted is the function moduleTimerHandler of the file src/module.c of the component Module Timer Subsystem. This manipulation causes double free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Patch name: b349fe2821e3998534b1454c1b64a478daf8c6b7. To fix this issue, it is recommended to deploy a patch.

    • Обновитесь до 9.1.2-1
    Опубликовано Обновлено
  19. CVE-2026-82631

    Низкий · CVSS 2.1EPSS 0,55%Есть исправление

    valkey-io valkey Blocked-on-keys blocked.c handleClientsBlockedOnKey use after free

    A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The patch is identified as b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b. Applying a patch is advised to resolve this issue.

    • Обновитесь до 9.1.2-1
    Опубликовано Обновлено
  20. CVE-2026-81934

    Высокий · CVSS 7.5EPSS 0,48%Есть исправление

    Redis TLS pending-data list use-after-free

    Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server.

    • Обновитесь до 5:6.0.16-1ubuntu1.2
    • Обновитесь до 5:7.0.15-1ubuntu0.24.04.5
    • Обновитесь до 5:7.0.15-1~deb12u10
    • Обновитесь до 5:8.0.2-3+deb13u3
    • Обновитесь до 5:8.0.5-1ubuntu0.1
    • Обновитесь до 5:8.0.6-3
    • Обновитесь до 6.2.24
    • Обновитесь до 7.8.6-303
    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →