CVE-2017-7922

Exploitation likely. EPSS gives it a 9.6% chance of exploitation in the next 30 days. No fix published yet.

CVSS 3.07.6High EPSS percentile95th9.6% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known FixNone yetNo fix or workaround published

Published 2017-06-21Updated 2026-05-13Sources: CVE.org, NVD, CSAF

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

n/a Cambium Networks ePMPAffected: Cambium Networks ePMPUpgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Identify which Cambium Networks ePMP devices you run (epmp 1000/epmp 2000, and any epmp elevate) and check their current firmware version.
Determine whether SNMP is enabled and how it is reachable (which network segments, firewall rules, and whether SNMP is accessible from the public internet).
Change SNMP community strings to strong, non-default values and ensure they are not shared more broadly than necessary.
Restrict SNMP access so it is reachable only from approved management systems (deny all other sources at the firewall/network level).
If you do not actively need SNMP, disable SNMP on the ePMP device(s) and remove any firewall rules that expose it.

May need vendor or contractor work

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

An Improper Privilege Management issue was discovered in Cambium Networks ePMP. The privileges for SNMP community strings are not properly restricted, which may allow an attacker to gain access to sensitive information and possibly allow for configuration changes.

In plain language

Written by AI from the record

CVE-2017-7922 is a Cambium Networks ePMP weakness where SNMP community settings may be given too much access, which can let an attacker read sensitive info and potentially change device settings. If your business uses ePMP and SNMP is reachable from the network, you should take action (at least tighten access and review configuration).

CVE-2017-7922 is an Improper Privilege Management issue in Cambium Networks ePMP where SNMP community strings are not properly privilege-restricted, enabling attackers who can reach the SNMP service with those credentials to access sensitive information and possibly perform configuration changes.

If you're affected

Sensitive device information exposure
Possible configuration changes
Operational disruption
Increased account/device takeover risk

What is it

SNMP is a common “management channel” used to monitor network devices. In this issue, the SNMP access tokens (“community strings”) may not be limited correctly—like giving someone an access badge that shouldn’t open certain doors. If an attacker can reach that management channel, they may be able to view sensitive device information and possibly alter settings.

Who is affected

This matters if your small business uses Cambium Networks ePMP devices (including epmp 1000, epmp 2000, and epmp elevate, plus epmp 1000 hotspot firmware) and you have SNMP enabled for monitoring or management. The risk is higher when SNMP can be reached from outside your tightly controlled management network (for example, from the internet or from untrusted network segments). The typical “gate” for exploitation is reachability to the SNMP service and misuse of the SNMP community configuration.

How urgent is it

Treat this as an AMBER issue: it’s a real privilege-handling flaw with potential for sensitive information exposure and configuration changes. There is no known public exploit code in the provided sources, and it is not listed in CISA KEV, but press attention is rising—so you should tighten exposure now rather than waiting for a patch. Because no fix information is available here, your near-term mitigation should focus on limiting who can reach SNMP and rotating/removing community access as appropriate.

What to do — in detail

Confirm you are in scope
- For each Cambium Networks ePMP device you operate (epmp 1000, epmp 2000, epmp elevate, and epmp 1000 hotspot firmware), record the exact firmware version from the device management interface.
- Cross-check whether SNMP is enabled on the device.
Check exposure and reachability
- Verify whether SNMP is reachable only from approved management hosts (your monitoring server(s), NMS, or jump box).
- Confirm SNMP is not reachable from the public internet.
- Review firewall/network rules: block SNMP (UDP ports typically used by SNMP) from all other source networks.
Reduce the SNMP “blast radius”
- Rotate SNMP community strings away from defaults.
- Use unique community strings per device (or per management domain) so one compromise doesn’t spread.
- Ensure community strings are not reused across unrelated devices or third-party systems.
Prefer disabling SNMP if not needed
- If you do not require SNMP for monitoring, disable SNMP on the ePMP device and remove any network rules that allow SNMP.
Firmware update planning (patch status unknown here)
- No fix/patch information was available in the provided sources, so you should contact Cambium support or consult Cambium’s security advisories for the recommended firmware upgrade for CVE-2017-7922.
- If/when a fixed firmware is identified by Cambium, schedule an upgrade and document any changes required for management/monitoring tools.
What to monitor
- Logs (on the ePMP device if available) for unusual SNMP requests or repeated failed access attempts.
- Network monitoring for unexpected SNMP traffic sources.
- Any configuration changes that occur outside your normal maintenance windows.

Technical context

CVE-2017-7922 is categorized as CWE-269 (Improper Privilege Management) in Cambium Networks ePMP. The core mechanism is that SNMP community strings are not properly restricted in privilege, so an attacker who can access SNMP with the community configuration may be able to read sensitive information and possibly make configuration changes. The provided sources report no public exploit code and no KEV listing, while press attention is rising. The predicted exploitation likelihood in the provided material (EPSS) is not a guarantee of real-world exploitation, and KEV/news data (if later confirmed) would override prediction for urgency. Fix information (a specific fixed firmware version) was not available in the provided sources, so remediation should rely on access restriction/disablement and community string hygiene until vendor guidance is obtained.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS95th

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

9.6% chance of exploitation activity in the next 30 days, which ranks it in the 95th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

23 events over 3381 days, from the signal feeds we watch.

2026-09-23EPSS band changemoderate → 0epss band change
2026-09-21EPSS band change0 → moderateepss band change
2026-09-06EPSS band changemoderate → 0epss band change
2026-09-05EPSS band change0 → moderateepss band change
2026-08-31EPSS band changemoderate → 0epss band change
2026-08-29EPSS band changelow → moderate

Affected products

cambium networkscommercialaka cnmaestro, cnpilot, epmp

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

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

Scored 7.6 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required LowRequires basic user-level privileges
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity LowData modification is possible but limited in scope or consequence
Availability LowReduced performance or intermittent disruption of service