p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de la pila ruby · Página 3

Vulnerabilidades publicadas para ruby en los últimos 30 días: 53. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 1143

  1. CVE-2026-126062

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

    Nokogiri : Possible SSRF on JRuby when resolving external DTDs or entities with `NONET` set

    Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.5, on JRuby, applications that parse untrusted XML with DTDLOAD, DTDVALID, or NOENT can have the NONET restriction bypassed when an external DTD or entity uses a short-form IPv4 host or uses absolute paths resolved against a network URL. The resolver can treat these identifiers as local and send a network request, potentially enabling server-side request forgery. CRuby and default parse options are not affected. This issue is fixed in version 1.19.5.

    • Actualiza a 1.19.5
    Publicación Actualización
  2. CVE-2026-125111

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

    Rack: Multipart parsing allows DoS via unbounded scan buffer growth

    Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser can retain parsed data in its internal StringScanner buffer when reads end inside or immediately after multipart headers. An unauthenticated attacker can align many small parts with rack.multipart.buffer_size boundaries so the buffer grows with the request despite per-field, header, and preamble limits, causing a worker to exhaust memory. The attack requires only a well-formed multipart body and affects applications that parse multipart requests. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

    • Actualiza a 2.2.25
    • Actualiza a 3.1.23
    • Actualiza a 3.2.8
    • Actualiza a 3.2.8-1
    Publicación Actualización
  3. CVE-2026-125110

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

    Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch

    Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Static serves a path after Utils.clean_path_info normalization but evaluates header_rules against a path that is only URL-decoded. An unauthenticated attacker can request a known file through raw or percent-encoded dot segments and receive it without path-specific security headers such as Content-Disposition or Content-Security-Policy. Applications that do not use path-specific header_rules are not affected. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

    • Actualiza a 2.2.25
    • Actualiza a 3.1.23
    • Actualiza a 3.2.8
    • Actualiza a 3.2.8-1
    Publicación Actualización
  4. CVE-2026-125109

    Media · CVSS 4.8EPSS 0,29%Corrección disponible

    Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835

    Rack is a modular Ruby web server interface. From 3.0 until 3.1.23 and 3.2.8, Rack::Request#host_with_port, #base_url, and #url can return an attacker-controlled invalid authority from Host, X-Forwarded-Host, or Forwarded: host= verbatim. Applications without an independent host allowlist that use these methods for absolute URLs, redirects, or origin-dependent checks can emit attacker-chosen delimiters, enabling redirect manipulation, string-based allowlist bypass, or unescaped markup reflection. Rails overrides these methods and is not expected to be affected. This issue is fixed in versions 3.1.23 and 3.2.8.

    • Actualiza a 3.1.23
    • Actualiza a 3.2.8
    • Actualiza a 3.2.8-1
    Publicación Actualización
  5. CVE-2026-125108

    Baja · CVSS 3.7EPSS 0,32%Corrección disponible

    Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass

    Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Multipart::Parser.parse_boundary can skip a leading empty or quoted boundary parameter in a multipart Content-Type header and accept a later parameter. Rack can therefore parse a request body with a boundary that a conforming intermediary would not derive, allowing form fields or file uploads to reach an application without the intended proxy or web application firewall inspection. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

    • Actualiza a 2.2.25
    • Actualiza a 3.1.23
    • Actualiza a 3.2.8
    • Actualiza a 3.2.8-1
    Publicación Actualización
  6. CVE-2026-63183

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

    OmniAuth: Host Header Injection Vulnerability

    OmniAuth is a flexible authentication system utilizing Rack middleware. Prior to 2.2.0, OmniAuth derives provider callback URLs from request-controlled host information when neither a fixed full_host nor framework-level incoming host validation is configured. A remote unauthenticated client can supply a forged Host header, creating a host header injection risk in applications whose web framework does not verify incoming host headers. Applications using appropriately configured Rails host authorization or a fixed full_host are not affected by this path. This issue is fixed in version 2.2.0.

    • Actualiza a 2.2.0
    Publicación Actualización
  7. CVE-2026-122006

    Crítica · CVSS 9.8EPSS 0,73%Código de explotación públicoCorrección disponible

    CVE-2026-122006

    The activestorage gem before 8.1.4.1 for Ruby on Rails, when ImageMagick attachment processing occurs, can allow server read and write operations (e.g., reading secret_key_base) because the ImageMagick analyzer runs when a file is attached, and there is not an ImageMagick security policy to block unintended functionality.

    • Actualiza a 8.0.5.2
    • Actualiza a 8.1.4.1
    Publicación Actualización
  8. CVE-2026-63414

    Alta · CVSS 7.6EPSS 0,57%Corrección disponible

    Shopify App: Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps

    Shopify App is a Rails engine for building Shopify applications. From 22.1.0 until 23.0.3, `token-exchange` authenticated controllers can expose a request-derived `shop` context instead of the identity from a verified Shopify ID token or active Shopify session. `current_shopify_domain` can resolve to the sanitized `shop` query parameter, so a request authenticated for one `shop` can cause application code to treat a different requested `shop` as current. Affected applications use `shopify_app` `token-exchange` authentication, accept authenticated requests with a `shop` query parameter, and rely on `current_shopify_domain` or `params[:shop]` f

    • Actualiza a 23.0.3
    Publicación Actualización
  9. CVE-2026-61848

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

    Crass: Non-ASCII characters cause superlinear CPU consumption

    Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when Crass parses input containing `non-ASCII characters`, inefficiencies in tracking the positions of `multi-byte characters` result in superlinear parsing time. An attacker-controlled CSS input consisting of many `non-ASCII characters` can therefore cause excessive CPU consumption and potentially denial of service. This issue is fixed in version 1.0.7.

    • Actualiza a 1.0.7
    • Actualiza a 1.0.7-1
    Publicación Actualización
  10. CVE-2026-61847

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

    Crass: A large number of adjacent CSS comments can trigger a SystemStackError

    Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments by recursively consuming the next token. An attacker-provided stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`, denying service to the parsing application. Preserving comments avoids this recursive path. This issue is fixed in version 1.0.7.

    • Actualiza a 1.0.7
    • Actualiza a 1.0.7-1
    Publicación Actualización
  11. CVE-2026-61846

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

    Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage

    Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, Crass recursively parses `CSS simple blocks and functions` without a depth guard. An attacker-controlled CSS value containing deeply nested blocks or functions can recurse until Ruby raises `SystemStackError`: stack level too deep, or cause excessive memory usage. Version 1.0.7 adds a configurable depth limit with a conservative default. This issue is fixed in version 1.0.7.

    • Actualiza a 1.0.7
    • Actualiza a 1.0.7-1
    Publicación Actualización
  12. CVE-2026-61845

    Alta · CVSS 8.9EPSS 0,39%Corrección disponible

    Crass: Large numeric exponents cause CPU and memory denial of service

    Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, Crass converts `CSS scientific notation` number values with unbounded exponentiation before clamping the result to `Float::MAX`. Applications that use Crass to parse attacker-controlled CSS strings can be forced to spend disproportionate CPU and memory parsing a tiny input, potentially resulting in a crash. This issue is fixed in version 1.0.7.

    • Actualiza a 1.0.7
    • Actualiza a 1.0.7-1
    Publicación Actualización
  13. CVE-2026-116695

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

    Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass

    Crass is a Ruby CSS parser that is compliant with the CSS Syntax Level 3 specification. Prior to 1.0.8, Crass incorrectly treats a closing parenthesis after an escaped backslash as escaped while consuming the remnants of a bad URL. Crass therefore keeps declarations, style rules, or at-rules inside a bad URL token even though a browser treats them as live CSS. A sanitizer that parses untrusted CSS with Crass and reserializes it without rejecting the bad URL can allow CSS used for UI redress, external resource loading, or CSS-based data exfiltration, but this issue does not enable script execution in modern browsers. This issue is fixed in ver

    • Actualiza a 1.0.8
    • Actualiza a 1.0.8-1
    Publicación Actualización
  14. CVE-2026-107715

    Media · CVSS 6.8EPSS 0,5%Corrección disponible

    Mechanize sends credential headers to another host after an HTTP redirect

    The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanize#request_headers= is reapplied by Mechanize::HTTP::Agent#request_add_headers even after Mechanize::HTTP::Agent#response_redirect strips per-request headers, and the protected header lists omit Proxy-Authorization and Cookie2. An attacker who controls a redirect target can capture bearer tokens or session cookies supplied through request_headers= or the per-request headers argument, while Mechanize#cookie_jar and Mechanize::HTTP::AuthStore are not affect

    • Actualiza a 2.14.1
    • Actualiza a 2.14.1-1
    Publicación Actualización
  15. CVE-2026-107399

    Media · CVSS 6.8EPSS 0,36%Corrección disponible

    Mechanize sends credential headers to another origin after a meta refresh

    The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agent#response_follow_meta_refresh when Mechanize#follow_meta_refresh is enabled. A page containing a meta refresh to another origin causes headers configured through Mechanize#request_headers= to be reapplied to the refresh request, allowing an attacker who controls content in the crawl to capture bearer tokens or session cookies. The default configuration is not affected because follow_meta_refresh is false, and the exposure is limited to caller-supplied default headers. This issue is fixed

    • Actualiza a 2.14.1
    • Actualiza a 2.14.1-1
    Publicación Actualización
  16. GHSA-mwm8-39rw-8826

    Media · CVSS 6.3Corrección disponible

    sqlite3-ruby: Use-After-Free in SQLite Aggregate Arguments in Heap-Allocated Argument Array

    ## Summary Using `Database#create_aggregate`, `#create_aggregate_handler`, or `Database#define_aggregator` to define an aggregate function that takes two or more arguments, and then evaluating it over TEXT or BLOB column values, can free the Ruby objects holding those arguments while a later argument is still being converted, during ordinary garbage collection. The aggregate's `step` method then receives an incorrect object, or the process crashes with a segmentation fault. ## Mitigation Upgrade to sqlite3 gem v2.9.6 or later. There is no reliable workaround. If you cannot upgrade, avoid defining aggregate functions that take two or more

    • Actualiza a 2.9.6
    Publicación Actualización
  17. CVE-2026-55107

    Crítica · CVSS 10EPSS 0,8%Corrección disponible

    Kobako Vulnerable to Sandbox Escape: guest eval reaches host RCE via method_missing → public_send (any bound Service)

    Kobako is a Ruby gem that embeds a Wasm-isolated mruby interpreter inside applications, allowing execution of untrusted Ruby scripts (LLM-generated code, user formulas, student submissions, third-party plugins) in-process without giving them access to host memory, files, network, or credentials. From version 0.1.0 to before version 0.9.1, a guest mruby script running inside the Kobako sandbox can execute arbitrary Ruby in the host process, fully escaping the sandbox. This issue has been patched in version 0.9.1.

    • Actualiza a 0.9.1
    Publicación Actualización
  18. CVE-2026-77602

    Crítica · CVSS 9.9EPSS 0,72%Código de explotación públicoCorrección disponible

    OpenC3 COSMOS: Authenticated remote code execution via the user-writable config overlay (table definitions, cmd/tlm definitions, and script suites)

    OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. From 5.1.0 until 7.3.0, authenticated non-administrator users can write content under targets_modified/ that is later executed by multiple configuration paths below the intended code-execution privilege tier. Table and command or telemetry definitions are processed through ConfigParser, PacketConfig, GENERIC_READ_CONVERSION, or GENERIC_WRITE_CONVERSION, allowing ERB rendering or Ruby and Python evaluation, while openc3-cosmos-script-runner-api/scripts/run_suite_analysis.rb executes suite procedure files through require. Stor

    • Actualiza a 7.3.0
    Publicación Actualización
  19. CVE-2026-77601

    Alta · CVSS 8.8EPSS 0,63%Código de explotación públicoCorrección disponible

    OpenC3 COSMOS: Authenticated OS command injection via the `pypi_url` setting

    OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. From 5.12.0 until 7.3.0, an authenticated actor can write the pypi_url setting through set_setting at POST /openc3-api/api, then cause OpenC3::PluginModel.install_phase2 in openc3/lib/openc3/models/plugin_model.rb to interpolate the value into a shell command while installing a plugin with Python dependency metadata. Shell metacharacters in the setting are interpreted by the command shell, allowing arbitrary operating-system commands to run as the openc3 service user with access to Redis and bucket credentials. Open-source d

    • Actualiza a 7.3.0
    Publicación Actualización
  20. CVE-2026-61570

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

    MPXJ: XXE Vulnerability in MerlinReader

    MPXJ is an open source library to read and write project plans from a variety of file formats and databases. From 5.5.5 until 16.4.1, MerlinReader creates a DocumentBuilder with default settings while parsing XML from the ZTIMEINTERVALS column of a Merlin project SQLite database, leaving doctype declarations and external entities enabled. A crafted database can cause the parser to read an arbitrary local file, although MPXJ's subsequent handling of the parsed XML makes disclosure of the file contents unlikely. This issue is fixed in version 16.4.1.

    • Actualiza a 16.4.1
    Publicación Actualización

Comprueba tu servidor

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

Comprueba tu servidor →