dbcve.org
Infinera Mtc 9 FirmwareOperating system · Nokia

CVE-2025-26489

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-08
Fix available
A fix is available. Upgrade to 23.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper input validation in the Netconf service in Infinera MTC-9 allows remote authenticated users to crash the service and reboot 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 · moderate confidence

The Infinera MTC-9 Netconf service has an improper input validation vulnerability that allows remote authenticated users to send crafted XML payloads. These malicious payloads cause the Netconf service to crash and force the appliance to reboot, creating a denial-of-service condition. Affected versions range from R22.1.1.0275 through versions before R23.0.

MitigationUpgrade Infinera MTC-9 firmware to R23.0 or later to remediate this vulnerability. Until patched, restrict access to the Netconf service to only trusted, authenticated users and consider network segmentation to limit exposure.

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
Infinera Mtc 9 FirmwareOperating system
Affected:>= 22.1.1.0275, < 23.0

CVSS 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Infinera MTC-9 device model
    Access the device management interface or CLI and identify the hardware model. Verify the device is an Infinera MTC-9 platform.
    Affected if The device model is not Infinera MTC-9, as this vulnerability affects only that specific product.
  2. Check installed firmware version
    Use the device CLI, web interface, or SNMP to retrieve the current firmware version. Compare the version number against the affected range R22.1.1.0275 through versions before R23.0.
    Affected if The firmware version is >= R22.1.1.0275 and < R23.0, placing the device within the vulnerable version range.
  3. Verify Netconf service status
    Check if the Netconf service is enabled and running on the device. Look for port 830 (NETCONF-over-SSH) or port 22 if Netconf is configured.
    Affected if The Netconf service is active, as the vulnerability requires the service to be running to receive the crafted XML payloads.
  4. Assess Netconf service exposure
    Review firewall rules, access control lists, or network segmentation configuration to determine if the Netconf service is accessible from untrusted networks.
    Affected if The Netconf service is reachable from remote or untrusted network segments, allowing remote authenticated attackers to deliver malicious payloads.
  5. Confirm remote authentication is permitted
    Examine the authentication and authorization configuration for the Netconf service to verify that remote user authentication is enabled.
    Affected if Remote authentication is allowed for Netconf users, as the vulnerability requires an authenticated user session to send the crafted XML.

A user is affected if the device is an Infinera MTC-9 running firmware version R22.1.1.0275 or later but earlier than R23.0, with the Netconf service exposed to remote authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.0 or later
Fixed in 23.0
Interim mitigation

Upgrade Infinera MTC-9 firmware to R23.0 or later to remediate this vulnerability. Until patched, restrict access to the Netconf service to only trusted, authenticated users and consider network segmentation to limit exposure.

Recommended fix Moderate confidence

R23.0

  1. Verify current firmware version by accessing the MTC-9 device management interface or using appropriate CLI commands
  2. Review Infinera release notes and upgrade documentation for R23.0 before proceeding
  3. Plan maintenance window as upgrade will require service reboot
  4. Download R23.0 firmware from Infinera's official support portal or authorized distribution channel
  5. Follow Infinera's standard firmware upgrade procedure for MTC-9 devices, typically via web UI or CLI
  6. After upgrade, verify the Netconf service is operational and confirm the new version is R23.0
  7. Test Netconf functionality with normal operations to ensure service stability
Caveat Check release notes for any configuration or feature changes between your current version and R23.0; test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infinera Mtc 9 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26489 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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