dbcve.org
MaasApplication · Canonical

CVE-2025-7044

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 3.3.11 / 3.4.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An Improper Input Validation vulnerability exists in the user websocket handler of MAAS. An authenticated, unprivileged attacker can intercept a user.update websocket request and inject the is_superuser property set to true. The server improperly validates this input, allowing the attacker to self-promote to an administrator role. This results in full administrative control over the MAAS deployment.

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 · high confidence

Improper input validation in MAAS's user websocket handler allows authenticated users to inject the is_superuser property into user.update requests, bypassing server-side authorization checks and enabling self-promotion to administrator privileges.

MitigationImplement strict server-side authorization checks that prevent non-admin users from modifying their own is_superuser status; validate all user-supplied properties against the caller's actual permissions.

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
MaasApplication
Affected:>= 3.3.0, < 3.3.11>= 3.4.0, < 3.4.9>= 3.5.0, < 3.5.9>= 3.6.0, < 3.6.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MAAS version
    Run 'maas --version' or check the package version via 'dpkg -l maas' or 'snap list maas' depending on installation method
    Affected if The installed version falls within any of these ranges: 3.3.0 to 3.3.10, 3.4.0 to 3.4.8, 3.5.0 to 3.5.8, or 3.6.0 to 3.6.1
  2. Verify websocket API accessibility
    Confirm the MAAS websocket API endpoint is reachable (typically at /ws/ or /api/2.0/websocket/)
    Affected if The websocket handler is exposed and accepts authenticated user requests
  3. Enumerate superuser accounts
    Run 'maas admin users list' or query the API endpoint '/api/2.0/users/' to list all users with is_superuser=True
    Affected if There are superuser accounts that should not have administrator privileges based on your organization's user management policy
  4. Review audit logs for privilege escalation
    Check MAAS audit logs for entries containing 'user.update' calls that modified the 'is_superuser' property, or search system logs for unauthorized permission changes
    Affected if There are log entries showing non-admin users successfully changing their own is_superuser status

You are affected if your MAAS version is 3.3.0-3.3.10, 3.4.0-3.4.8, 3.5.0-3.5.8, or 3.6.0-3.6.1 and you have unexpected administrator accounts or audit evidence of unauthorized privilege escalation via the websocket API.

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.

dbcve · scoped
Upgrade available Upgrade to 3.3.11 / 3.4.9 / 3.5.9 or later
Fixed in 3.3.113.4.93.5.9
Interim mitigation

Implement strict server-side authorization checks that prevent non-admin users from modifying their own is_superuser status; validate all user-supplied properties against the caller's actual permissions.

Recommended fix High confidence

Upgrade to 3.3.11 (for 3.3.x), 3.4.9 (for 3.4.x), 3.5.9 (for 3.5.x), or 3.6.2 (for 3.6.x) depending on your current branch

  1. Identify current MAAS version using 'maas --version' or the web UI
  2. Determine which version branch you're on (3.3.x, 3.4.x, 3.5.x, or 3.6.x)
  3. Create a backup of the MAAS database and configuration before upgrading
  4. Schedule a maintenance window for the upgrade
  5. For Debian/Ubuntu packages: Run 'sudo apt update' and 'sudo apt upgrade maas'
  6. Alternatively, follow the official MAAS upgrade documentation for your deployment method
  7. After upgrade, verify the version matches the fixed release
  8. Log in as an administrator and confirm the is_superuser field cannot be modified through the user.update websocket method
Caveat Standard MAAS upgrade may require database migration; review release notes for any breaking changes between minor versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maas Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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