ACTIONMAILBOX · GHSA-5957-c7qm-m469 · Package
FIX → 8.1.4.1 +1
Action Mailbox's Mailgun ingress signs the timestamp and token without a separator, so a captured signed webhook can be replayed with a future timestamp and accepted indefinitely. An attacker holding one signed Mailgun request could submit arbitrary inbound email that the app processes as genuine.
first public Nov 4, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that receive inbound email through the Action Mailbox Mailgun ingress are affected. Apps that do not use Mailgun ingress, or that take inbound email another way, can skip it. Teams whose server clock runs more than 2 minutes behind Mailgun's will start rejecting genuine webhooks after the fix and should sync their clock.
Not affected if no-mailgun-ingress, other-inbound-email-provider
Who cares action-mailbox, mailgun, rails, self-hosted
actionmailbox version in Gemfile.lock against the ranges below.config.action_mailbox.ingress = :mailgun or a Mailgun route to /rails/action_mailbox/mailgun/inbound_emails/mx.Upgrade to 8.1.4.1 +1
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.
The fixed releases also reject a Mailgun request whose timestamp is more than 2 minutes ahead of the server's clock, as they already did for one more than 2 minutes behind it. An application whose clock runs more than 2 minutes behind Mailgun's will now reject genuine webhooks and should synchronize its clock.
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
actionmailbox 8.1 series: upgrade to 8.1.4.1actionmailbox 8.0 series: upgrade to 8.0.5.2This issue was responsibly reported by HackerOne researcher davutselcuk.