CVE-2026-54649Network attack vector

Private inbox disclosure via dropped Reply-To header

Published Sep 17, 2026 · Updated Sep 17, 2026

Information disclosure in PunchIn-App punchin-email before 1.5.0 allows remote attackers to expose the operator's private inbox address. The handleInbound path adds Reply-To, but message.forward() silently drops that header, so a reply is addressed directly from the configured FORWARD_TO inbox. The attacker must email an alias and receive an operator reply; only the operator's address is disclosed, without third-party data access.

CVSS severity2.1
Low
EPSS probability0.84%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Information disclosure in PunchIn-App punchin-email before 1.5.0 allows remote attackers to expose the operator's private inbox address. The handleInbound path adds Reply-To, but message.forward() silently drops that header, so a reply is addressed directly from the configured FORWARD_TO inbox. The attacker must email an alias and receive an operator reply; only the operator's address is disclosed, without third-party data access.

The record

CVE
CVE-2026-54649
Published
Sep 17, 2026
Updated
Sep 17, 2026
Vendor
PunchIn-App
Product
punchin-email
Classifications
CWE-201, CWE-200, T1589.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.5.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

PunchIn-App · punchin-emailversion=< 1.5.0

Published CVSS scores

2.1GitHubCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-201Insertion of Sensitive Information Into Sent Data
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1589.002Gather Victim Identity Information: Email Addresses

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started