CVE-2026-25702
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 · uneditedA Improper Access Control vulnerability in the kernel of SUSE SUSE Linux Enterprise Server 12 SP5 breaks nftables, causing firewall rules applied via nftables to not be effective.This issue affects SUSE Linux Enterprise Server: from 9e6d9d4601768c75fdb0bad3fbbe636e748939c2 before 9c294edb7085fb91650bc12233495a8974c5ff2d.
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 confidenceAn Improper Access Control vulnerability in the SUSE Linux Enterprise Server 12 SP5 kernel breaks nftables, the Linux packet filtering framework. This allows firewall rules applied via nftables to be ineffective, bypassing intended network security controls. The flaw exists in kernel commits between 9e6d9d4601768c75fdb0bad3fbbe636e748939c2 and 9c294edb7085fb91650bc12233495a8974c5ff2d.
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= 12CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the installed SUSE kernel versionRun 'uname -r' to get the kernel version, or check /proc/version. For SUSE, also use 'cat /etc/os-release' to confirm SLES 12.Affected if The kernel version is within the vulnerable range for SLES 12 SP5 (kernel commits between 9e6d9d4601768c75fdb0bad3fbbe636e748939c2 and 9c294edb7085fb91650bc12233495a8974c5ff2d) and has not been patched.
-
Verify nftables is in useRun 'nft list ruleset' to see if any nftables rules are configured. Also check 'which nft' to confirm nftables is installed.Affected if nftables is actively used with firewall rules configured.
-
Confirm nftables service is enabledRun 'systemctl is-enabled nftables' or check if nft module is loaded via 'lsmod | grep nft'. Check if nftables service is active with 'systemctl status nftables'.Affected if nftables service is enabled and running with rules loaded.
-
Test if nftables filtering is actually workingCreate a simple test rule to block specific traffic (e.g., block incoming ICMP to loopback), then attempt that traffic from another source. Alternatively, compare nft list ruleset output with actual network behavior using packet capture (tcpdump).Affected if Rules appear in 'nft list ruleset' but traffic that should be blocked is still allowed through, indicating rules are ineffective.
A user is affected if they are running an unpatched SLES 12 kernel within the vulnerable commit range and are using nftables with rules that are not actually filtering traffic as expected.
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 the SUSE kernel security update that includes the fix for this vulnerability. After updating, verify nftables rules are correctly filtering traffic and functioning as intended.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25702 — 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-25702 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