Unauthenticated API access via loose key comparison
Published Aug 8, 2026 · Updated Aug 8, 2026
Authentication bypass in Tribulant Software Newsletters before 4.16 allows remote attackers to perform privileged API actions. The API authentication path loosely compares a client-supplied key with the configured secret, allowing PHP type coercion to satisfy the check. Exploitation requires the optional JSON API to be enabled and permits subscriber-record changes or unauthorized email sending.
Summary
What happened
Authentication bypass in Tribulant Software Newsletters before 4.16 allows remote attackers to perform privileged API actions. The API authentication path loosely compares a client-supplied key with the configured secret, allowing PHP type coercion to satisfy the check. Exploitation requires the optional JSON API to be enabled and permits subscriber-record changes or unauthorized email sending.
The record
- CVE
- CVE-2026-16269
- Published
- Aug 8, 2026
- Updated
- Aug 8, 2026
- Vendor
- Tribulant Software
- Product
- Newsletters
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2026CVE publishedPublication date reported by the CVE source.
- Aug 8, 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.
- Affected versionversion=0 <4.16
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo