Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
CVE-2026-126068: Rails Action Mailbox Mailgun ingress allows forged emails
CVE-2026-126068 · published 11 days ago
Summary
The Mailgun integration in Rails Action Mailbox can be tricked into accepting a forged email if an attacker reuses a captured signed request and changes its timestamp. This lets the attacker submit false messages that appear to come from any sender. Upgrade to Rails 8.1.4.1 or 8.0.5.2, or apply the vendor’s patch, to stop the problem.
What to do
- Update actionmailbox to version 8.1.4.1.
- Update actionmailbox to version 8.0.5.2.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | rails | rails | >= 8.1, < 8.1.4.1 |
| rubygems | – | actionmailbox |
>= 8.1.0.beta1, < 8.1.4.1 < 8.0.5.2 Fix: upgrade to 8.1.4.1
|
| Debian:12 | debian | rails | All versions |
| Ubuntu:Pro:16.04:LTS | canonical | rails | All versions |
Original advisory text
Action Mailbox: Possible signature replay in Action Mailbox Mailgun ingress
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.
References
- https://github.com/rails/rails/security/advisories/GHSA-5957-c7qm-m469 Vendor Advisory
- https://github.com/rails/rails/commit/4aa2ec66822bc4eb8b341a0608f1c90a3e371a34 Patch
- https://github.com/rails/rails/releases/tag/v8.0.5.2 URL
- https://github.com/rails/rails/releases/tag/v8.1.4.1 URL
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionmailbox/GHSA-...
- https://github.com/advisories/GHSA-5957-c7qm-m469
- https://security-tracker.debian.org/tracker/CVE-2026-126068 Vendor Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/126xxx/CVE-2026-1260... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-126068 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-126068 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-126068 Third Party Advisory
- https://github.com/rails/rails/commit/c3a295c5c22266e8ec4d0e664e6923a299235e7a Patch
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-294Authentication Bypass by Capture-replay
Timeline
Published10 Nov 2026
Updated22 Nov 2026
First seen10 Nov 2026
Sources
CVE-2026-126068 · NVD
CVE-2026-126068 · MITRE
GHSA-5957-c7qm-m469 · GHSA
DEBIAN-CVE-2026-126068 · OSV
CVE-2026-126068 · OSV
UBUNTU-CVE-2026-126068 · OSV
Track software like this
Free during beta