LiveActive security incident?Get immediate response
CVE Record

CVE-2025-42599: Active!

Active! mail 6 BuildInfo: 6.60.05008561 and earlier contains a stack-based buffer overflow vulnerability. Receiving a specially crafted request created and sent by a remote unauthenticated attacker may lead to arbitrary code execution and/or a denial-of-service (DoS) condition.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-42599 is a critical flaw in QUALITIA Active! mail 6. A remote attacker who is not logged in can send a crafted request that may crash the service or run code on the server. CISA lists it as known exploited, so this should be treated as urgent for any exposed deployment.

Executive priority

Immediate action is warranted for any affected deployment, especially if externally reachable. The combination of unauthenticated remote code execution potential, denial-of-service impact, and CISA KEV listing makes this a business continuity and compromise risk.

Technical view

Active! mail 6 BuildInfo 6.60.05008561 and earlier has a stack-based buffer overflow, CWE-121. The CVSS 3.0 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Reported impacts are arbitrary code execution and denial of service.

Likely exposure

Exposure applies to QUALITIA Active! mail 6 BuildInfo 6.60.05008561 and earlier. Risk is highest where the service can receive requests from untrusted or internet-facing networks. The source bundle does not identify other affected products or versions.

Exploitation context

CISA KEV status indicates known exploitation. The provided sources do not include exploit details, observed campaigns, affected organizations, or attacker tooling. Treat internet-reachable instances as high-priority until vendor guidance is applied.

Researcher notes

Evidence supports a critical stack-based buffer overflow in Active! mail 6 with unauthenticated network reachability and possible RCE or DoS. KEV supports active exploitation, but public source details in the bundle do not describe exploit mechanics, indicators, or patch specifics.

Mitigation direction

  • Inventory all Active! mail 6 instances and record BuildInfo versions.
  • Review QUALITIA and JVN advisories for fixed builds or official mitigations.
  • Apply vendor remediation as soon as it is available and tested.
  • Reduce untrusted network reachability until remediation is complete.
  • Monitor CISA KEV and vendor updates for changed guidance.

Validation and detection

  • Confirm whether any instance runs BuildInfo 6.60.05008561 or earlier.
  • Verify whether each instance is reachable from untrusted networks.
  • Check change records for applied vendor remediation or compensating controls.
  • Review service logs for crashes, abnormal requests, or unexpected process behavior.
  • Track remediation status against KEV-driven urgency.
Prepared
Reviewed
Confidence
high
Sources
5

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-42599 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.0)
Known Exploited
Yes
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9.8Critical
CVSS 3.0 vector shape for CVE-2025-42599Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
QUALITIA CO., LTD.Active! mail 6BuildInfo: 6.60.05008561 and earlierListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.