CVE-2025-40898
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 Import Arc data archive functionality due to insufficient validation of the input file. An authenticated user with limited privileges, by uploading a specifically-crafted Arc data archive, can potentially write arbitrary files in arbitrary paths, altering the device configuration and/or affecting its 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 Import Arc data archive functionality where insufficient validation of uploaded archive contents allows an authenticated low-privilege user to craft a malicious Arc archive containing path traversal sequences (e.g., ../../../'), enabling arbitrary file writes to locations outside the intended upload directory.
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.5.0< 25.5.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 versionRun 'nozomi-version' or check the UI footer for version number. Confirm the product is either Nozomi Networks CMC or Guardian.Affected if The installed version is less than 25.5.0
-
Check if Import Arc feature is accessibleNavigate to the data import or archive import section of the web UI. Verify if an authenticated user (even low-privilege) can access the Import Arc data archive functionality.Affected if The Import Arc data archive feature is enabled and accessible to the user in question
-
Verify upload directory integrityInspect the designated archive upload directory (typically /var/opt/nozomi/uploads or similar) for any files created outside the expected directory structure. Use 'find / -path /*/..' to detect files with unusual path references.Affected if Files exist outside the intended upload directory, particularly with paths containing '../' sequences
-
Review audit logs for archive importsCheck system or application audit logs for Import Arc operations. Look for entries containing '../' or path traversal patterns in filenames.Affected if Logs show archive imports with path traversal sequences in filenames
A user is affected if they run CMC or Guardian with version lower than 25.5.0 and the Import Arc data archive feature is enabled, allowing authenticated low-privilege users to potentially write files outside the intended directory.
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.5.0
Implement strict validation of archive contents and sanitize all file paths within the archive to prevent directory traversal sequences; restrict write operations to a designated safe directory and verify the final resolved path is within allowed boundaries.
25.5.0
- Upgrade Cmc to version 25.5.0 or later
- Upgrade Guardian to version 25.5.0 or later
- After upgrading, verify the Import Arc data archive functionality works correctly
- Test that the path traversal vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40898 — 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-40898 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