rails · Ruby on Rails · published 2026-11-10

CVE-2026-126068Action Mailbox: Possible signature replay in Action Mailbox Mailgun ingress

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-126068 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 28% of all CVEs. This Ruby on Rails vulnerability: CVSS 3.7 (v3.1). Fixed upstream in Ruby on Rails 8.1.4.1, 8.0.5.2; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Ruby on Rails 8.1.4.1, 8.0.5.2.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixierailsNo fix yet
12 bookwormrailsNo fix yet
Ubuntu26.04 LTSrailsNo fix yet
24.04 LTSrailsNo fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Web frameworkRuby on Rails

    Ruby on Rails security releases: 8.1.4.1, 8.0.5.2

    Upgrade to 8.1.4.18.0.5.2

    Why: Vendor security release for server software (most severe: CVE-2026-126186).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (29th pct)FIRST EPSS v2026.06.15
CVSS base score3.7 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →