EUVD-2026-82386Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Confidentiality-only leak of the operator's own address, triggered by the operator's own reply (UI:R); no integrity or availability impact and no attacker privileges needed.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
Information disclosure in punchin-email prior to 1.5.0 leaks the operator's private inbound inbox address (the FORWARD_TO value) to any correspondent who receives a reply from the alias. The Cloudflare Email Worker's handleInbound path used message.forward(), which silently strips the added Reply-To header, so when the operator hits Reply their mail client sends directly from the secret forwarding address instead of re-entering the relay; the issue is fixed in 1.5.0. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires the punchin-email Cloudflare Email Worker running a version prior to 1.5.0 where handleInbound uses message.forward() (which drops the added Reply-To) instead of rewriting and re-sending the raw message. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuinely low-priority issue and the signals are internally consistent. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade to punchin-email 1.5.0 (release tag v1.5.0; fix commit 593685ffc0b8eb3949a4838e7bfe1e97b953d084, pull request 66) per the GitHub advisory GHSA-2ph7-69xm-hmwv - the release replaces the handleInbound message.forward() call with a raw-message rewrite plus send via EMAIL_SENDING so the alias is used as From and relay+<id>@RELAY_DOMAIN as Reply-To, fully closing the leak path. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today