Threats / Qualitia / CVE-2025-42599
CVE-2025-42599
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Qualitia Active! Mail vulnerability
Qualitia Active! Mail contains a stack-based buffer overflow vulnerability allowing remote unauthenticated attackers to execute arbitrary code or cause denial of service.
Verdict
Today item — known-exploited.
A remote, unauthenticated attacker can exploit a stack-based buffer overflow in Qualitia Active! Mail via specially crafted requests to achieve arbitrary code execution or trigger service disruption.
CISA KEV Yes · 2025-04-285EPSS 0.03215 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-28).
Probability (EPSS)
EPSS 0.03215 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Qualitia, Active! Mail. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-121 Stack-based Buffer Overflow — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 10 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request designed to overflow the stack buffer in the mail service.
Business
The organization's mail service becomes vulnerable to unauthorized access and control.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send the payload to the unauthenticated endpoint without requiring credentials.
Business
Authentication controls fail to prevent exploitation, expanding the attack surface.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code on the affected system or crash the mail service.
Business
Critical business communications are disrupted or compromised, affecting operations and data integrity.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05