dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-49603

CRITICAL · 9.1 CVSS v3.1 Published 2025-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Northern.tech Mender Server before 3.7.11 and 4.x before 4.0.1 has Incorrect Access Control.

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

Mender Server before 3.7.11 and 4.x before 4.0.1 contains an Incorrect Access Control vulnerability allowing unauthorized users to bypass authorization checks and access sensitive IoT device management functionality or data they should not have permission to view or modify.

MitigationUpgrade Mender Server to version 3.7.11 or later, or 4.0.1 or later, to resolve the access control flaw.

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

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

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

  1. Identify Mender Server installation
    Check if Mender Server is running in your environment by querying the service API at your Mender endpoint, or inspect running containers/pods labeled 'mender-server' or 'mender' in your container orchestration system.
    Affected if Mender Server is installed and running in your environment
  2. Retrieve the installed Mender Server version
    Query the Mender Server API endpoint /api/management/v1/internal/version or check the version from your deployment configuration files, container image tags, or Helm chart values if deployed via Kubernetes.
    Affected if Unable to determine the version from API or deployment configuration
  3. Compare version against affected ranges
    If the version starts with '3.x', verify it is below 3.7.11. If the version starts with '4.x', verify it is below 4.0.1. Any version before 3.7.11 (e.g., 3.7.10, 3.6.x, 3.5.x) or any 4.x version below 4.0.1 is affected.
    Affected if Version is below 3.7.11 (for 3.x releases) OR version is below 4.0.1 (for 4.x releases)
  4. Verify authorization configuration
    Review Mender Server user roles, permissions, and API token configurations in the deployment to confirm access control policies are in place. This vulnerability allows bypassing these checks, so even if policies exist, the server may still be vulnerable if the version is affected.
    Affected if Mender Server is configured with user roles or API access controls that restrict sensitive device management functions

You are affected if your Mender Server version is below 3.7.11 (for 3.x releases) or below 4.0.1 (for 4.x releases), and the server exposes management APIs to users or integrations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mender Server to version 3.7.11 or later, or 4.0.1 or later, to resolve the access control flaw.

Recommended fix Moderate confidence

Mender Server 3.7.11 (for 3.x branches) or Mender Server 4.0.1 (for 4.x branches)

  1. Identify your current Mender Server version by checking the deployment configuration or Mender UI
  2. If running Mender Server 3.x: Plan upgrade to version 3.7.11 or later
  3. If running Mender Server 4.x: Plan upgrade to version 4.0.1 or later
  4. Review Mender upgrade documentation for your deployment type (Docker, Kubernetes, or binary)
  5. Execute the upgrade following the official migration/upgrade guide
  6. Verify the upgrade completed successfully by checking the Mender Server version
  7. Confirm that access controls are functioning correctly post-upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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