CVE-2026-35506
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 · uneditedELECOM wireless LAN access point devices contain an OS command injection vulnerability in processing of ping_ip_addr parameter. If processing a crafted request sent by a logged-in user, an arbitrary OS command may be executed.
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 confidenceELECOM wireless LAN access points contain an OS command injection vulnerability in the ping_ip_addr parameter processing. An authenticated user can inject arbitrary OS commands through the ping functionality, potentially compromising the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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.
-
Confirm ELECOM wireless LAN access point modelIdentify the exact model number of the ELECOM access point by checking the device label, web management interface header, or SNMP sysDescr. Cross-reference with ELECOM product documentation to confirm it is a wireless LAN access point.Affected if The device is an ELECOM wireless LAN access point and the specific model falls within the affected product line.
-
Verify web management interface accessibilityAttempt to access the device's web-based administration interface (typically HTTP/HTTPS on ports 80 or 443, or a custom management port). Check if the login page or admin dashboard is reachable from the network.Affected if The management interface is exposed and reachable on the network.
-
Locate ping diagnostic functionalityLog into the admin interface and navigate through the menu options to find ping or network diagnostics tools. Common paths include Maintenance > Diagnostics, Tools > Ping, or Network Settings > Ping Test.Affected if The ping diagnostic feature is present and accessible within the authenticated admin panel.
-
Verify authentication requirement for ping featureCheck whether the ping functionality is accessible only after providing valid administrator credentials. Attempt to access the ping feature directly without logging in or after session timeout to confirm authentication is enforced.Affected if The ping feature can be accessed by an authenticated user (legitimate user or compromised credentials).
-
Check for firmware version disclosureLocate the firmware version information in the admin interface (typically under Status > System, Maintenance > Firmware, or About page). Compare the installed firmware version against any available vendor release notes or security advisories.Affected if Firmware version cannot be determined or matches unpatched versions that contain the command injection vulnerability.
You are affected if you have an ELECOM wireless LAN access point with an accessible web management interface where authenticated users can access the ping diagnostic feature, as the vulnerability allows OS command injection through the ping_ip_addr parameter.
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.
From vendor dataApply vendor firmware patches when available. Restrict administrative access to the device management interface to trusted IP addresses/users only. Consider network segmentation to limit exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35506 — 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-2026-35506 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