CVE-2026-129054
validatedZero produced an exploit or a check.GHSA-2pcf-qv33-v899 ↗EUVD-2026-131748 ↗
description
AcyMailing SMTP Newsletter versions through 11.1.0 are affected by a flaw that can expose sensitive information included in transmitted data. A remote attacker may retrieve embedded sensitive data without authentication; the advisory does not state additional preconditions.
mitigation
Restrict public network access to AcyMailing SMTP Newsletter and limit use to trusted users and networks until an update is available. Review sent data and associated logs for unintended disclosure, as no fixed version is recorded.
outcome
Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-20 19:00Zcve_org: trigger signal, started the run
- 2026-11-20 19:39Z
this entry in the feed
GET /api/v1/feed/CVE-2026-129054
{ "etk_id": "ETK-2026-5084", "cve_id": "CVE-2026-129054", "display_id": "CVE-2026-129054", "ghsa_id": "GHSA-2pcf-qv33-v899", "euvd_id": "EUVD-2026-131748", "status": "published", "anchor_state": "anchored", "title": "Sensitive information exposure in AcyMailing SMTP Newsletter", "summary": "AcyMailing SMTP Newsletter versions through 11.1.0 are affected by a flaw that can expose sensitive information included in transmitted data. A remote attacker may retrieve embedded sensitive data without authentication; the advisory does not state additional preconditions.", "mitigation": "Restrict public network access to AcyMailing SMTP Newsletter and limit use to trusted users and networks until an update is available. Review sent data and associated logs for unintended disclosure, as no fixed version is recorded.", "vendor": "Datasolution", "product": "AcyMailing SMTP Newsletter", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 11.1.0" ], "ecosystem": null, "fixed_versions": [], "package_name": "acymailing", "purl": null } ], "cwes": [ 201 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "upstream", "exploit": false, "pipeline_minutes": 0.03601685, "t0_at": "2026-11-20T19:00:13.939000+00:00", "signals": { "check": { "at": "2026-11-20T19:39:52.062700+00:00", "days": 0.02752457986111111, "is_lower_bound": false, "measured_at": "2026-11-20T19:00:13.939000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-20T19:00:13.939000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-20T19:00:13.939000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-129054" } } }
published 2026-11-20 19:39Z
last change 2026-11-20 22:31Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.