p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de la pile ruby · Page n° 6

Vulnérabilités publiées pour ruby au cours des 30 derniers jours : 53. Présentes dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 1143

  1. CVE-2026-63119

    Moyenne · CVSS 6.2EPSS 0,19%Correctif disponible

    MCP Ruby SDK: Unbounded line buffer in stdio transports leads to memory exhaustion (DoS)

    MCP Ruby SDK is the official Ruby SDK for Model Context Protocol servers and clients. Prior to 0.23.0, MCP::Server::Transports::StdioTransport and MCP::Client::Stdio in the mcp gem use IO#gets without a byte limit, allowing a peer that sends data without a newline to exhaust process memory. This issue is fixed in version 0.23.0.

    • Mettez à jour vers 0.23.0
    Publication Mise à jour
  2. CVE-2026-67430

    Moyenne · CVSS 5.3EPSS 0,37%Correctif disponible

    MCP Ruby SDK: Unbounded session retention in StreamableHTTPTransport allows memory exhaustion via initialize flood

    MCP Ruby SDK is the official Ruby SDK for Model Context Protocol servers and clients. Prior to 0.23.0, MCP::Server::Transports::StreamableHTTPTransport in the mcp gem does not expire sessions by default, so repeated initialize requests retain unbounded ServerSession objects and can exhaust process memory. This issue is fixed in version 0.23.0.

    • Mettez à jour vers 0.23.0
    Publication Mise à jour
  3. CVE-2026-63118

    Moyenne · CVSS 6.9EPSS 0,24%Correctif disponible

    MCP Ruby SDK: Streamable HTTP transport lacks DNS-rebinding (Host/Origin) protection

    MCP Ruby SDK is the official Ruby SDK for Model Context Protocol servers and clients. Prior to 0.23.0, MCP::Server::Transports::StreamableHTTPTransport in the mcp gem does not validate the HTTP Host or Origin request headers, which allows a malicious browser page to use DNS rebinding to reach a locally running MCP server and invoke exposed tools. This issue is fixed in version 0.23.0.

    • Mettez à jour vers 0.23.0
    Publication Mise à jour
  4. GHSA-pmwx-rm49-xv39

    Faible · CVSS 2.3Correctif disponible

    ActiveRecord::Tenanted::Storage::DiskService#path_for has a possible path traversal

    ### Summary Active Record Tenanted's override of Active Storage's `DiskService#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. ### Mitigation Upgrade to Active Record Tenanted v0.7.0 or later. As a workaround, do not use untrusted user input as blob keys. Blob keys are expected to be trusted strings. ### Credit

    • Mettez à jour vers 0.7.0
    Publication Mise à jour
  5. CVE-2026-54659

    Moyenne · CVSS 6.9EPSS 0,37%Correctif disponible

    Pagy I18n locale option is not validated before being used in a file path

    Pagy is agnostic pagination in plain Ruby. From 43.0.0 until 43.5.6, Pagy::I18n.locale= in gem/lib/pagy/modules/i18n/i18n.rb stored locale values verbatim and later used them as <locale>.yml path components, allowing untrusted params[:locale] values with absolute paths or ../ sequences to create a file existence and readability oracle for YAML files. This issue is fixed in version 43.5.6.

    • Mettez à jour vers 43.5.6
    Publication Mise à jour
  6. CVE-2026-54603

    Élevée · CVSS 8.6EPSS 0,45%Correctif disponible

    OAuth2::Client#request: Protocol-relative redirect Location overrides authority, leaking bearer Authorization to attacker host

    OAuth2 is a Ruby wrapper for the OAuth 2.0 and 2.1 authorization frameworks, including OpenID Connect (OIDC). From 0.4.0 to 2.0.21, a protocol-relative redirect Location returned to OAuth2::Client#request overrides the request authority, so the bearer Authorization header is sent to an attacker-controlled host, leaking the credential. This issue is fixed in version 2.0.22.

    • Mettez à jour vers 1.4.4-1+deb12u1
    • Mettez à jour vers 2.0.22
    • Mettez à jour vers 2.0.25-1
    Publication Mise à jour
  7. CVE-2026-54605

    Élevée · CVSS 7.2EPSS 0,19%Correctif disponible

    OAuth: Cross-origin token-request redirects can expose signed request metadata

    OAuth is a Ruby wrapper for the OAuth 1.0 and 1.0a protocols, providing clients and servers. From 0.5.5 to 1.1.5, OAuth::Consumer#token_request parses the raw Location header of a 300 to 399 redirect returned by the OAuth server and follows the redirect recursively, which can mutate the consumer's configuration and expose signed OAuth request metadata, including the Authorization header, to a cross-origin host. This issue is fixed in version 1.1.6.

    • Mettez à jour vers 1.1.6
    Publication Mise à jour
  8. CVE-2026-54620

    Faible · CVSS 2EPSS 0,14%Correctif disponible

    sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks

    sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5.

    • Mettez à jour vers 2.9.5
    • Mettez à jour vers 2.9.5-1
    Publication Mise à jour
  9. CVE-2026-54619

    Faible · CVSS 2EPSS 0,14%Correctif disponible

    sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity

    sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5.

    • Mettez à jour vers 2.9.5
    • Mettez à jour vers 2.9.5-1
    Publication Mise à jour
  10. CVE-2026-55518

    Critique · CVSS 9.6EPSS 0,41%Correctif disponible

    Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation

    Avo is a framework to create admin panels for Ruby on Rails apps. Prior to 3.32.1 and 4.0.0.beta.51, Avo's association attach workflow checks attach_<association>? in the UI and GET /resources/:resource/:id/:related/new path, but the actual write endpoint, POST /resources/:resource/:id/:related, does not run the same authorization check before mutating the association through Avo::AssociationsController#create. An authenticated low-privileged Avo user can bypass hidden or disabled attach controls and directly attach related records to a parent record by sending a crafted POST request, which can lead to privilege escalation and cross-tenant da

    • Mettez à jour vers 3.32.1
    • Mettez à jour vers 4.0.0.beta.51
    Publication Mise à jour
  11. CVE-2026-54498

    Élevée · CVSS 8.7EPSS 0,45%Correctif disponible

    view_component: around_render HTML-Safety Bypass

    view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails. From 4.0.0 until 4.12.0, ViewComponent::Base#around_render can return HTML-unsafe strings that bypass the escaping behavior applied to normal #call return values. This creates an XSS risk when downstream applications use around_render to wrap, replace, instrument, or conditionally return content that includes user-controlled data, and ViewComponent::Collection#render_in can amplify the issue by joining per-item results and marking the entire output html_safe, converting raw unsafe output into an ActiveSupport::SafeBuffer. This iss

    • Mettez à jour vers 4.12.0
    Publication Mise à jour
  12. CVE-2026-54497

    Moyenne · CVSS 6.8EPSS 0,33%Correctif disponible

    view_component: Reused Component Instances Retain Stale Render Context

    view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails. From 4.0.0 until 4.12.0, ViewComponent::Base instances retain render-scoped objects across calls to render_in; if the same component, collection, or spacer component instance is reused across requests, users, tenants, or threads, later renders can use stale helpers, controller, request, view_flow, format/variant details, and slot child context from an earlier render. This can cause authorization-aware components to render privileged UI for a lower-privileged user, generate links using a stale Host header, leak slot/helper state, a

    • Mettez à jour vers 4.12.0
    Publication Mise à jour
  13. CVE-2026-53727

    Élevée · CVSS 8.9EPSS 0,51%Correctif disponible

    css_parser: SSRF and Local File Disclosure in `CssParser::Parser#read_remote_file`

    css_parser is a Ruby CSS parser. From 2.2.0 until 3.0.0, CssParser::Parser#read_remote_file in lib/css_parser/parser.rb, and therefore load_uri! and the @import-following branch of add_block!, issued HTTP and HTTPS requests against any host, port, and URI without a scheme allowlist, host or IP filtering, or protection against link-local, loopback, or RFC-1918 addresses. Location: redirects were followed recursively back into the same function, which also serviced file:// URIs, so a single attacker-controlled HTTP redirect could upgrade the bug from SSRF to arbitrary local file disclosure. Any consumer of css_parser that hands it attacker-infl

    • Mettez à jour vers 3.0.0
    • Mettez à jour vers 3.0.0-1
    Publication Mise à jour
  14. CVE-2026-54163

    Moyenne · CVSS 4.7EPSS 0,21%Correctif disponible

    secure_headers: CSP directive injection via sandbox, plugin_types, and report_to when given untrusted input

    secure_headers manages application of security headers with many safe defaults. Prior to 7.3.0, secure_headers builds the Content-Security-Policy value by stitching directives with ; separators, and build_sandbox_list_directive, build_media_type_list_directive, and build_report_to_directive interpolate caller-supplied strings without scrubbing ;, \r, or \n. When untrusted input reaches SecureHeaders.override_content_security_policy_directives or append APIs for :sandbox, :plugin_types, or :report_to, an attacker can inject a CSP directive such as script-src 'unsafe-inline' * before the legitimate script-src, enabling XSS reachability through

    • Mettez à jour vers 7.3.0
    • Mettez à jour vers 7.3.0-1
    Publication Mise à jour
  15. CVE-2026-54171

    Moyenne · CVSS 6.5EPSS 0,43%Correctif disponible

    Excon: redact additional sensitive/risky headers when following redirects

    Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial request includes header information that is not intended for the new target. This issue is fixed in version 1.5.0.

    • Mettez à jour vers 1.5.0
    • Mettez à jour vers 1.5.0-1
    Publication Mise à jour
  16. CVE-2026-54465

    Moyenne · CVSS 6.3EPSS 0,49%Correctif disponible

    websocket-driver: Memory exhaustion in HTTP header parser

    websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, when websocket-driver is used to implement a WebSocket server on top of a TCP server using WebSocket::Driver.server() or to complement a WebSocket client, a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory. This issue is fixed in version 0.8.1.

    • Mettez à jour vers 0.8.1
    • Mettez à jour vers 0.8.1-1
    Publication Mise à jour
  17. CVE-2026-54463

    Moyenne · CVSS 6.9EPSS 0,49%Correctif disponible

    websocket-driver: Memory exhaustion via abuse of protocol length headers

    websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.

    • Mettez à jour vers 0.8.1
    • Mettez à jour vers 0.8.1-1
    Publication Mise à jour
  18. CVE-2026-54464

    Moyenne · CVSS 6.3EPSS 0,45%Correctif disponible

    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

    • Mettez à jour vers 0.8.1
    • Mettez à jour vers 0.8.1-1
    Publication Mise à jour
  19. CVE-2026-45363

    Critique · CVSS 9.1EPSS 0,36%Correctif disponible

    `jwt` (Ruby gem) - empty-key HMAC bypass

    ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0.

    • Mettez à jour vers 1.0.0-3ubuntu0.1~esm1
    • Mettez à jour vers 1.5.6-1ubuntu0.1~esm1
    • Mettez à jour vers 2.1.0-2ubuntu0.1~esm1
    • Mettez à jour vers 2.10.3
    • Mettez à jour vers 2.2.2-1ubuntu0.1~esm1
    • Mettez à jour vers 2.5.0-1+deb12u1
    • Mettez à jour vers 2.7.1-1+deb13u1
    • Mettez à jour vers 2.7.1-1+deb13u1build0.24.04.1
    • Mettez à jour vers 2.7.1-1+deb13u1build0.26.04.1
    • Mettez à jour vers 3.2.0
    • Mettez à jour vers 3.2.0-1
    Publication Mise à jour
  20. CVE-2026-47736

    Élevée · CVSS 7.5EPSS 0,35%Correctif disponible

    Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion

    Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, when PROXY protocol v1 support is enabled, Puma reads incoming bytes into an internal buffer while waiting for CRLF to determine whether a PROXY v1 line is present, allowing an attacker that continuously sends bytes without CRLF to cause unbounded in-process memory growth and additional CPU cost from repeatedly scanning the growing buffer. This issue is fixed in versions 7.2.1 and 8.0.2.

    • Mettez à jour vers 5.6.5-3+deb12u2
    • Mettez à jour vers 7.2.1
    • Mettez à jour vers 8.0.2
    • Mettez à jour vers 8.0.2-1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →