CVE-2025-40889
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA path traversal vulnerability was discovered in the Time Machine functionality due to missing validation of two input parameters. An authenticated user with limited privileges, by issuing a specifically-crafted request, can potentially alter the structure and content of files in the /data folder, and/or affect their availability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability exists in the Time Machine functionality where two input parameters are not validated, allowing authenticated low-privilege users to manipulate file paths using traversal sequences (e.g., ../../) to access or modify files outside the intended /data directory bounds.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 25.2.0< 25.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionDetermine if your installation is Nozominetworks Cmc or Nozominetworks Guardian, then check the installed version numberAffected if The product is Cmc or Guardian and the version is below 25.2.0
-
Confirm Time Machine feature accessVerify whether the Time Machine functionality is accessible to authenticated users in your deploymentAffected if Time Machine is enabled and accessible to authenticated users
-
Verify low-privilege user accessCheck if low-privilege or non-administrator accounts can interact with the Time Machine featureAffected if Authenticated low-privilege users can access Time Machine parameters
-
Inspect Time Machine input parametersReview the Time Machine feature code or configuration to locate the two input parameters that handle file pathsAffected if The parameters do not validate or sanitize path traversal sequences such as ../
-
Test path boundary enforcementIf you have a test environment, attempt to access a file outside the /data directory using traversal sequences in the Time Machine parametersAffected if Files outside /data can be accessed or manipulated through the Time Machine feature
You are affected if you are running Cmc or Guardian version below 25.2.0 with Time Machine accessible to authenticated users and the path parameters lack traversal sequence validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped25.2.0
Implement strict input validation and path sanitization for both affected parameters, ensuring paths are normalized, validated against an allowlist, and do not permit traversal sequences outside the intended directory.
Cmc 25.2.0 and Guardian 25.2.0
- 1. Identify the current version of Cmc or Guardian by accessing the admin console or using the system status command
- 2. Navigate to the official Nozomi Networks support portal or download center at security.nozominetworks.com
- 3. Download the fixed release version 25.2.0 for your specific product (Cmc or Guardian)
- 4. Review the upgrade documentation and release notes for version 25.2.0
- 5. Create a backup of the current configuration as a precaution
- 6. Execute the upgrade procedure following the product-specific installation instructions
- 7. Verify the installation completed successfully and the version shows 25.2.0
- 8. Confirm the Time Machine functionality is operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data