p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de la pila Bases de datos · Página 6

Vulnerabilidades publicadas para Bases de datos en los últimos 30 días: 109. Incluidas en el catálogo KEV: 0.

RSS ↗ JSON ↗
Filtrar vulnerabilidades
Bases de datos

Vulnerabilidades: 1413

  1. CVE-2026-66071

    Media · CVSS 6EPSS 0,47%Corrección disponible

    RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1, Atom exhaustion: OAuth2 JWT tag: scope values. extractscopes/1 parses scopes of the form .tag: and calls rabbitdatacoercion:toatom() to convert to a tag atom. The token signature is verified first, so the attacker cannot forge scopes , but in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one In deployments where users can influence the scopes included in their IdP-issued JWT rabbitmqauthbackendoauth2 enabled IdP permits attacker-influenced scope values in signed tokens. This is

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  2. CVE-2026-66078

    Baja · CVSS 2.1EPSS 0,38%Corrección disponible

    RabbitMQ: protected tag bypass via bulk-delete

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, protected tag bypass via bulk-delete. dELETE /api/users/:name refuses to delete users tagged protected (rabbitmgmtwmuser:deleteresource/2 checks isprotecteduser). POST /api/users/bulk-delete iterates the supplied username list and calls rabbitauthbackendinternal:deleteuser/2 directly , that function has no protected-tag check , so the guard is silently An administrator can delete protected-tagged service accounts via the bulk endpoint, bypassing a safeguard the test suite confirms is rabbitmqmanagement enabled Attacker has the administrato

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  3. CVE-2026-66073

    Media · CVSS 6EPSS 0,41%Corrección disponible

    RabbitMQ: Atom table exhaustion via management API node field

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, Atom table exhaustion via management API node field. pUT /api/queues/:vhost/:name (and the exchanges and bindings endpoints) accepts a node JSON field. The value goes through rabbitnodes:make → listtoatom with no cluster membership check first. Each unique value permanently leaks one atom. A March 2026 refactoring (ea61ce2563) introduced safe helpers in rabbitmgmtnodes.erl (parsenodename, safeatom, and requirenodename, using binarytoexistingatom) and fixed several callers (QQ replica ops, wmauthattempts, wmnodememoryets, getsortreverse, an

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  4. CVE-2026-67237

    Alta · CVSS 7.5EPSS 0,45%Corrección disponible

    RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint

    RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, set_token_auth/2 inserted a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without escaping, allowing attacker-controlled token content to execute JavaScript in the management UI origin. The endpoint is exposed before authentication only when management.oauth_enabled is true, and exploitation through the cookie path additionally requires the attacker to plant an access_token cookie on the management host. This issue is fixed in versions 4.2.8 and 4.3.2.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 3.12.1-1ubuntu1.7
    • Actualiza a 3.5.7-1ubuntu0.16.04.4+esm3
    • Actualiza a 3.6.10-1ubuntu0.5+esm1
    • Actualiza a 3.8.3-0ubuntu0.3+esm2
    • Actualiza a 3.9.27-0ubuntu0.6
    • Actualiza a 4.0.5-10ubuntu5.2
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  5. CVE-2026-67234

    Baja · CVSS 2.3EPSS 0,43%Corrección disponible

    RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference

    RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, get_auth_mechanism/1 used term_to_binary/1 on the strict_auth_mechanism or preferred_auth_mechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the browser from deleting the preference. The issue is not directly exploitable for code execution or data exfiltration; its security relevance is limited to stale authentication-mechanism preferences persisting across logout and login cycles. This issue is fixed in versions 4.2.8 and 4.3.2.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  6. CVE-2026-67225

    Media · CVSS 6.3EPSS 0,34%Corrección disponible

    RabbitMQ: Stream-protocol frame length never validated against frame_max

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  7. CVE-2026-67230

    Media · CVSS 6.3EPSS 0,58%Corrección disponible

    RabbitMQ: Web-STOMP unbounded pre-auth accumulation

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the Web STOMP WebSocket handler enforced neither max_frame_size nor login_timeout before authentication, allowing an unauthenticated client to keep a connection alive with a slow stream of small frames and accumulate unbounded pre-authentication state. The rabbitmq_web_stomp plugin must be enabled, and no authentication is required to reach the vulnerable path. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  8. CVE-2026-67222

    Media · CVSS 5.9EPSS 0,32%Corrección disponible

    RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client

    RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, mechanisms/1 applied list_to_atom/1 to every colon-delimited token in an attacker-controlled auth_mechanism value, permanently consuming Erlang VM atoms and allowing the node to be crashed with a large request. Exploitation requires the Shovel or Federation plugin to be in use, and setting auth_mechanism requires the policymaker tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  9. CVE-2026-67236

    Alta · CVSS 8.2EPSS 0,14%Corrección disponible

    RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login

    RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. This issue is fixed in versions 4.2.8 and 4.3.2.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 3.12.1-1ubuntu1.7
    • Actualiza a 3.5.7-1ubuntu0.16.04.4+esm3
    • Actualiza a 3.6.10-1ubuntu0.5+esm1
    • Actualiza a 3.8.3-0ubuntu0.3+esm2
    • Actualiza a 3.9.27-0ubuntu0.6
    • Actualiza a 4.0.5-10ubuntu5.2
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  10. CVE-2026-67233

    Media · CVSS 6EPSS 0,3%Corrección disponible

    RabbitMQ: Monitoring-tag user can DELETE shovels

    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 shovel management resource's is_authorized/2 delegates to rabbit_mgmt_util:is_authorized_monitor/2, which accepts the monitoring tag. But allowed_methods includes DELETE, and delete_resource/2 deletes / restarts shovel runtime parameters with no additional role check. A monitoring user , intended to have read-only visibility , can therefore delete or restart any shovel in any vhost they can see. A read-only monitoring user can delete or restart any dynamic shovel , a state-changing operation that the equivalent /api/parameters endpoi

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  11. CVE-2026-67221

    Media · CVSS 5.9EPSS 0,19%Corrección disponible

    RabbitMQ: AMQP 1.0 shovel status exposes plaintext URI passwords

    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, The AMQP 0-9-1 shovel calls amqp_uri:remove_credentials before storing its connection URI, but the AMQP 1.0 shovel stores the raw URI including the password. The stored URI is visible via GET /api/shovels and via rabbitmqctl shovel_status. Preconditions include The Shovel plugin must be in use with AMQP 1.0 shovels configured using URI-embedded credentials. Reading the exposed status requires the monitoring tag.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  12. CVE-2026-67231

    Crítica · CVSS 9.1EPSS 0,23%Corrección disponible

    RabbitMQ: Trust-store whitelist by Issuer+Serial only

    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, The trust-store plugin installs a verify_fun that overrides {bad_cert, unknown_ca} / {bad_cert, selfsigned_peer} when the presented cert "matches" a whitelisted one. The match key is extract_issuer_id/1 → public_key:pkix_issuer_id/2 → {IssuerName, SerialNumber} , both fields are taken verbatim from the presented certificate body and contain no public-key, SKI, fingerprint or signature material. is_whitelisted/1 is a pure ets:member lookup; the stored full DER is used only for list/0 display and is never compared against the presented cer

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 3.12.1-1ubuntu1.7
    • Actualiza a 3.5.7-1ubuntu0.16.04.4+esm3
    • Actualiza a 3.6.10-1ubuntu0.5+esm1
    • Actualiza a 3.8.3-0ubuntu0.3+esm2
    • Actualiza a 3.9.27-0ubuntu0.6
    • Actualiza a 4.0.5-10ubuntu5.2
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  13. CVE-2026-67218

    Baja · CVSS 2.1EPSS 0,37%Corrección disponible

    RabbitMQ: Super-stream HTTP creation skips configure-permission check

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely. A user with management tag and vhost access , but no configure permission on any resource , can crea

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  14. CVE-2026-66074

    Media · CVSS 6EPSS 0,38%Corrección disponible

    RabbitMQ: ReDoS via management API ?name= filter

    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, match_value/3 passes the user-supplied ?name= regular expression to re:run with no match_limit option, and executes it once per resource in the result set. OTP's default 10M match_limit caps each call at roughly 100-200ms, but the regex runs once per resource in the result set. With a large set, for example 5000 queues at 150ms each, a single request consumes 12 or more minutes of CPU. Parallel requests saturate the schedulers. The use_regex=true option is a supported feature on list endpoints, so this path is reachable through normal AP

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  15. CVE-2026-67232

    Alta · CVSS 8.2EPSS 0,4%Corrección disponible

    RabbitMQ: Web-MQTT decompression bomb

    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, The cowboy WebSocket options at line 117 set compress => true, enabling RFC 7692 permessage-deflate negotiation. The handler does not set max_frame_size, so cowboy's default of infinity applies. cowlib's cow_ws:parse_payload/9 calls zlib:inflate/2 on the compressed payload with no output-size limit. An attacker can negotiate permessage-deflate during the WebSocket upgrade and send a frame containing a zlib bomb (e.g. 50 KB → 5 GB). Decompression occurs in the connection process before websocket_handle/2 ever sees the MQTT bytes. An unaut

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 3.12.1-1ubuntu1.7
    • Actualiza a 3.5.7-1ubuntu0.16.04.4+esm3
    • Actualiza a 3.6.10-1ubuntu0.5+esm1
    • Actualiza a 3.8.3-0ubuntu0.3+esm2
    • Actualiza a 3.9.27-0ubuntu0.6
    • Actualiza a 4.0.5-10ubuntu5.2
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  16. CVE-2026-67405

    Media · CVSS 5.3EPSS 0,11%Corrección disponible

    RabbitMQ: CSWSH on Web-STOMP / Web-MQTT (no Origin validation)

    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, Neither the Web-MQTT handler (deps/rabbitmq_web_mqtt/src/rabbit_web_mqtt_handler.erl:104) nor the Web-STOMP handler (deps/rabbitmq_web_stomp/src/rabbit_web_stomp_handler.erl:102) validates the Origin header on the WebSocket upgrade. Under ssl_cert_login=true, the browser presents the client certificate automatically, so an attacker's JavaScript running in the victim's browser can authenticate as the victim. Preconditions include The non-default configuration use_http_auth=true (Web-STOMP) or ssl_cert_login=true (both plugins) must be ena

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  17. CVE-2026-66075

    Baja · CVSS 2.3EPSS 0,22%Corrección disponible

    RabbitMQ: Monitoring-tag user can restart federation links

    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, is_authorized/2 for the /federation-links/.../restart route uses is_authorized_monitor (accepts the monitoring tag), while allowed_methods permits DELETE and delete_resource/2 triggers rabbit_federation_link_sup:restart. There is no per-method elevation check and no comment marking it intentional. A read-only monitoring user can restart any federation link , a state-changing operation that disrupts message flow. Preconditions include rabbitmq_federation + rabbitmq_federation_management plugins enabled Attacker has credentials with the mo

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  18. CVE-2026-67219

    Media · CVSS 6EPSS 0,3%Corrección disponible

    RabbitMQ: Consistent-hash exchange unbounded weight

    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_binding/3 parses the routing key as an integer weight N and computes ring positions with lists:seq(NextN0, NextN0 + N - 1). validate_binding/2 only checks N >= 1 , no upper bound. The resulting list is stored in the exchange's Khepri record, replicated cluster-wide, and reloaded on restart. A user with write permission on a consistent-hash exchange and read on a queue can create a binding whose routing key (the hash-ring weight) is an arbitrarily large integer. The broker allocates a list of that many integers via lists:seq/2 and per

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  19. CVE-2026-67228

    Media · CVSS 6.9EPSS 0,28%Corrección disponible

    RabbitMQ: Atom exhaustion: to_atom on runtime-parameter component

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, The runtime-parameters lookup path coerces the URL :component segment to an atom with rabbit_data_coercion:to_atom/1 in lookup_component/1 (deps/rabbit/src/rabbit_runtime_parameters.erl), creating a new atom for any previously unseen value. A safe helper, rabbit_registry:binary_to_type/1, which uses binary_to_existing_atom with a catch, already exists but is not used at this call site. lookup_component/1 calls rabbit_data_coercion:to_atom(Component) on the :component segment of the request URL, converting an attacker-supplied string into a new atom. Because the E

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 4.3.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  20. CVE-2026-67235

    Alta · CVSS 7.1EPSS 0,3%Corrección disponible

    RabbitMQ: AMQP 0-9-1 body assembly never validates accumulated size

    RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQ

    rabbitmq rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-server rabbitmq-serverSistemas operativos Bases de datos
    • Actualiza a 3.12.1-1ubuntu1.7
    • Actualiza a 3.5.7-1ubuntu0.16.04.4+esm3
    • Actualiza a 3.6.10-1ubuntu0.5+esm1
    • Actualiza a 3.8.3-0ubuntu0.3+esm2
    • Actualiza a 3.9.27-0ubuntu0.6
    • Actualiza a 4.0.5-10ubuntu5.2
    • Actualiza a 4.3.0-2
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →