Skip to main content
VulnerabilityPublished Updated

CVE-2026-54649: punchin-email · Information Exposure

Affects punchin-emailSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 1.5.0 when convenient.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.5.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade punchin-email and punchin-app/punchin-email to 1.5.0.

Affected software

ProductAffectedFixed in
PunchIn-Apppunchin-emailAffected
  • <1.5.0
Fixed in
  • 1.5.0
GitHubpunchin-app/punchin-emailpkg:github/punchin-app/punchin-emailOther threatsAffected
  • <1.5.0
Fixed in
  • 1.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade punchin-email to version 1.5.0 or later, where this issue is fixed. Since punchin-email is a Cloudflare Email Worker (cloud service), the vendor manages remediation for this cloud-hosted service. Check the vendor advisory for confirmation and ensure the service is updated accordingly.

Description

punchin-email is a Cloudflare Email Worker that provides two-way role aliases while relaying mail to a private inbox. Prior to 1.5.0, handleInbound delivers inbound alias mail with message.forward(), which silently drops the added Reply-To header intended to route responses through the relay. When a correspondent sends mail to an alias and the operator replies, the mail client can send directly to the correspondent from the private FORWARD_TO inbox address, exposing that address. The disclosure is limited to the operator's own email address and does not expose third-party data or provide code execution or authentication bypass. This issue is fixed in version 1.5.0.

References

Community reviews

Loading reviews…