dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-67603

MEDIUM · 5.1 CVSS v4.0 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges 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
A Improper Authorization vulnerability in Foomuuri llows arbitrary users to influence the firewall configuration.This issue affects Foomuuri: from ? before 0.31.

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 confidence

Foomuuri is an nftables-based firewall management tool for Linux. This improper authorization vulnerability allows arbitrary or unauthorized users to influence/modify the firewall configuration. An attacker could potentially change firewall rules, expose services, or disable protection mechanisms.

MitigationUpgrade Foomuuri to version 0.31 or later which contains the authorization fix. Verify firewall rules remain intact after upgrade.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify Foomuuri is installed
    Check for the foomuuri binary or package on the system. On most systems, run: which foomuuri or rpm -qa | grep -i foomuuri or dpkg -l | grep -i foomuuri
    Affected if Foomuuri is not found on the system, then the vulnerability does not apply
  2. Determine installed Foomuuri version
    Run foomuuri --version or foomuuri -V to retrieve the installed version number
    Affected if The command fails or returns no version information, making it impossible to compare against the affected range
  3. Compare version against affected range
    Take the version number from the previous step and compare it to version 0.31. Versions before 0.31 are affected by this improper authorization vulnerability
    Affected if The installed version is lower than 0.31 (for example, 0.30, 0.29, etc.)
  4. Audit recent firewall configuration changes
    Review nftables ruleset and Foomuuri configuration files in /etc/foomuuri/ for any unauthorized or unexpected rule modifications. Check logs for firewall change events
    Affected if Unexpected or unauthorized firewall rules are present that were not intentionally configured by the administrator

A system is affected if Foomuuri is installed with a version lower than 0.31, as those versions contain the improper authorization flaw that allows unauthorized firewall modifications.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Foomuuri to version 0.31 or later which contains the authorization fix. Verify firewall rules remain intact after upgrade.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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