CVE-2025-26488
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 · uneditedImproper Input Validation vulnerability in Infinera MTC-9 allows remote unauthenticated users to crash the service and cause a reboot of the appliance, thus causing a DoS condition, via crafted XML payloads.This issue affects MTC-9: from R22.1.1.0275 before R23.0.
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 · high confidenceImproper input validation in Infinera MTC-9's XML parsing allows remote unauthenticated attackers to send crafted XML payloads that crash the service and force an appliance reboot, resulting in denial of service.
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>= 22.1.1.0275, < 23.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm Infinera MTC-9 modelAccess the device management interface or CLI and verify the model is MTC-9. Check system information or device status page.Affected if Device model is NOT MTC-9 (different models are not affected by this specific CVE)
-
Check firmware versionIn the device CLI or web interface, look for the firmware version information (typically under System > Software, Device Info, or 'show version' command).Affected if Firmware version is >= 22.1.1.0275 and < 23.0 (versions 22.1.1.0275 through 22.x are vulnerable; version 23.0 and later are fixed)
-
Verify XML parsing service is enabledCheck if the device management interface (typically web GUI or API endpoint) that processes XML requests is accessible and enabled. Look for XML-based configuration or provisioning features.Affected if XML parsing service is enabled and reachable over the network (this is the attack surface for the vulnerability)
-
Review for unexpected reboots or service crashesCheck system logs, boot logs, or crash logs for the MTC-9 device. Look for timestamps correlating with XML input attempts or service failures.Affected if Device has experienced unexplained service crashes or forced reboots with XML parsing in the error logs
You are affected if the device is an Infinera MTC-9 running firmware version 22.1.1.0275 through 22.x (any version below 23.0) and the XML management interface is accessible.
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 · scoped23.0
Upgrade MTC-9 to version R23.0 or later which contains the fix for this improper input validation vulnerability.
R23.0 or later
- Identify the current firmware version of the Infinera MTC-9 device
- Schedule a maintenance window for the firmware upgrade as this process may cause service interruption
- Download the R23.0 or later firmware version from Infinera's official support portal
- Follow Infinera's standard firmware upgrade procedure for MTC-9 devices
- Verify the upgrade was successful and the device is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26488 — 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-26488 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