CVE-2026-4948
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 flaw was found in firewalld. A local unprivileged user can exploit this vulnerability by mis-authorizing two runtime D-Bus (Desktop Bus) setters, setZoneSettings2 and setPolicySettings. This mis-authorization allows the user to modify the runtime firewall state without proper authentication, leading to unauthorized changes in network security configurations.
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 confidencefirewalld contains an authorization flaw in its D-Bus interface where the setZoneSettings2 and setPolicySettings runtime setters lack proper authentication checks. Local unprivileged users can exploit these mis-authorized D-Bus methods to modify runtime firewall state and network security configurations without credentials.
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= 7.0<= 2.4.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Verify firewalld is installedRun 'firewall-cmd --version' or check package with 'rpm -q firewalld'Affected if firewalld is not installed, the system is not affected by this vulnerability
-
Check installed firewalld versionCompare the output of 'firewall-cmd --version' or 'rpm -q --qf "%{VERSION}" firewalld' against the affected versions (RHEL 7.0 or firewalld <= 2.4.0)Affected if version is 2.4.0 or lower, or the system is RHEL 7.0 - the system may be affected
-
Confirm firewalld service is runningRun 'firewall-cmd --state' or 'systemctl is-active firewalld'Affected if firewalld is not running, the D-Bus interface is not active and the flaw cannot be exploited
-
Inspect D-Bus policy for setZoneSettings2 and setPolicySettingsExamine firewalld D-Bus policy files in /etc/dbus-1/system.d/ (typically firewalld.conf or org.fedoraproject.FirewallD1.conf) and verify whether these setter methods allow calls from unprivileged users or lack proper authorization checksAffected if D-Bus policy permits unprivileged users to invoke setZoneSettings2 or setPolicySettings without authentication, the system is vulnerable
The system is affected if firewalld version 2.4.0 or lower (or RHEL 7.0) is installed, the service is running, and the D-Bus authorization policy permits unprivileged local users to modify firewall settings via the vulnerable setters.
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 patches to firewalld that enforce proper authorization checks on the setZoneSettings2 and setPolicySettings D-Bus methods, ensuring only privileged users can modify runtime firewall settings.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4948 — 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-4948 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