Path Traversal in AcyMailing SMTP Newsletter (CVE-2026-95588)
Summary
Path traversal in AcyMailing SMTP Newsletter (CVE-2026-95588). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Unauthenticated Arbitrary File Deletion in AcyMailing SMTP Newsletter <= 11.0.5 versions.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-95588 was discovered in AcyMailing SMTP Newsletter.
In plain terms, it is a flaw that lets attackers reach files they should not see.
Severity is High (CVSS 8.6/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "AcyMailing SMTP Newsletter CVE-2026-95588".
CVE-2026-95588 (AcyMailing SMTP Newsletter). Severity: High / CVSSv3 8.6. Category: CWE-22.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-95588) in AcyMailing SMTP Newsletter. In plain words, it is a flaw that lets attackers reach files they should not see.
Target versions of AcyMailing SMTP Newsletter (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 8.6/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-22)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- web patchstack.com
- web nvd.nist.gov
- web github.com