dbcve.org
Mri 3t FirmwareOperating system · Philips

CVE-2021-26262

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 6.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Philips MRI 1.5T and MRI 3T Version 5.3 through 5.8.1 does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

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

Philips MRI 1.5T and MRI 3T scanners running software versions 5.3 through 5.8.1 contain a broken access control vulnerability where the system fails to properly restrict or incorrectly restricts access to sensitive resources from unauthorized actors, potentially allowing unauthenticated users to access restricted functionality or data.

MitigationUntil an official patch is available from Philips, implement network segmentation to isolate MRI systems from unauthorized network access and enforce strict access controls. Consult Philips for vendor-specific remediation guidance and scheduled patch releases.

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
Mri 3t FirmwareOperating system
Affected:>= 5.0.0, < 6.0.0
Mri 1.5t FirmwareOperating system
Affected:>= 5.0.0, < 6.0.0

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

CVSS:3.1/AV:L/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. Determine the MRI scanner firmware version
    Access the scanner's service interface or system information panel (typically accessible via the service menu or system administration console) and locate the firmware version field. Consult the scanner's documentation for the exact navigation path to view system version information.
    Affected if The displayed firmware version is 5.0.0 through 5.8.1 (any version >= 5.0.0 and < 6.0.0)
  2. Confirm the MRI scanner model type
    Identify whether the scanner is a Philips MRI 3T or MRI 1.5T model. This information is typically displayed on the system startup screen, on the scanner console, or in the system administration interface.
    Affected if The scanner is a Philips MRI 3T or MRI 1.5T running the affected firmware version from step 1
  3. Review network accessibility of the MRI system
    Examine the network configuration and firewall rules governing access to the MRI scanner. Determine if the scanner's management interfaces, service ports, or web interfaces are reachable from network segments outside of the trusted medical device network.
    Affected if The MRI scanner is reachable from network segments that contain unauthorized or untrusted users or systems
  4. Verify access control enforcement on scanner interfaces
    Test or inspect the scanner's authentication requirements for accessing administrative functions, service menus, or data export features. Attempt to determine if restricted resources can be accessed without valid credentials or from unauthorized network locations.
    Affected if The scanner allows access to restricted functionality without proper authentication or from unauthorized network locations

You are affected if your Philips MRI 3T or 1.5T scanner runs firmware version 5.0.0 through 5.8.1 and the system is accessible from unauthorized network segments.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Until an official patch is available from Philips, implement network segmentation to isolate MRI systems from unauthorized network access and enforce strict access controls. Consult Philips for vendor-specific remediation guidance and scheduled patch releases.

Recommended fix Moderate confidence

Firmware version 6.0.0 or later

  1. Contact Philips service or your authorized Philips service representative to schedule firmware upgrade to version 6.0.0 or later
  2. Verify that the upgrade package is officially signed and sourced from Philips
  3. Plan maintenance window as MRI systems require scheduled downtime for firmware updates
  4. After upgrade, verify system access controls are functioning correctly per Philips documentation
Caveat MRI firmware upgrades may require Philips engineering support and could have system-specific calibration implications; coordinate with Philips before upgrading

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

Fix this in Mri 3t Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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