dbcve.org
E5600 FirmwareOperating system · Linksys

CVE-2025-29227

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
In Linksys E5600 V1.1.0.26, the \usr\share\lua\runtime.lua file contains a command injection vulnerability in the runtime.pingTest function via the pt["pkgsize"] parameter.

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 confidence

A command injection vulnerability exists in the runtime.pingTest function in Linksys E5600 router firmware V1.1.0.26. The pt["pkgsize"] parameter in \usr\share\lua\runtime.lua is not properly sanitized before being used in system command execution, allowing arbitrary command injection.

MitigationUpdate router firmware to a patched version when available. If no patch exists, consider network segmentation to limit exposure to untrusted users and disable the affected pingTest functionality if possible.

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
E5600 FirmwareOperating system
Affected:= 1.1.0.26

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Identify router firmware version
    Log into the Linksys E5600 web admin interface (typically at 192.168.1.1) and navigate to Administration > Firmware Upgrade or Status page to view the current firmware version. Alternatively, check via CLI if telnet/ssh access is enabled.
    Affected if Firmware version is exactly 1.1.0.26
  2. Verify vulnerable file exists
    Access the router filesystem via telnet/ssh (if enabled) and check for the presence of /usr/share/lua/runtime.lua. Use command: ls -la /usr/share/lua/runtime.lua
    Affected if File /usr/share/lua/runtime.lua exists on the device
  3. Confirm pingTest function is exposed
    Check if the pingTest function is accessible via the router's web interface or API endpoints. This is typically found in network diagnostic features or when the ping functionality is available to authenticated users.
    Affected if pingTest or ping diagnostics feature is accessible via the router web interface or API
  4. Check for unauthenticated access vector
    Determine if the runtime.pingTest function can be invoked without authentication by attempting to access the relevant endpoint or reviewing the router's HTTP service configuration.
    Affected if The pingTest endpoint is reachable without authentication or with low-privilege user access

The router is affected if it runs firmware version 1.1.0.26 and contains the vulnerable runtime.lua file with the unprotected pingTest function accessible to 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update router firmware to a patched version when available. If no patch exists, consider network segmentation to limit exposure to untrusted users and disable the affected pingTest functionality if possible.

Recommended fix Moderate confidence

Check vendor for firmware version > 1.1.0.26

  1. Check Linksys support website (support.linksys.com) for the latest E5600 firmware version
  2. If a firmware version newer than 1.1.0.26 is available, download it from the official vendor source
  3. Access the router web interface (typically at 192.168.1.1)
  4. Navigate to Administration > Firmware Upgrade
  5. Upload and apply the new firmware version
  6. After reboot, verify the router is functioning normally
  7. Alternatively, if no update is available, consider network-level mitigations such as restricting WAN access to the router's management interface
Caveat Firmware upgrades on routers can sometimes reset configuration; backup settings before upgrading

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

Fix this in E5600 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29227 — 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-29227 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