# CVE-2021-26262: Philips MRI 1.5T and 3T Improper Access Control

> An unauthorized actor can access restricted resources on Philips MRI scanners due to improper access control restrictions.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2021
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-gggj-fp2x-7www

## What is CVE-2021-26262?

CVE-2021-26262 is a medium-severity missing authorization vulnerability in Philips MRI 1.5T, published on 19 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-286 (Incorrect User Management)

## Which versions are affected by CVE-2021-26262?

It affects 2 products.


Products: Philips Mri 1.5t Firmware, Philips Mri 3t Firmware.

## How do I fix CVE-2021-26262?

No fix has been published for CVE-2021-26262 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-26262 being exploited?

There is no known exploitation of CVE-2021-26262 in the wild and no public exploit code.

## Other vulnerabilities in Philips MRI 1.5T

- [CVE-2021-26248](https://insights.sbomify.com/CVE-2021-26248/): Philips MRI 1.5T and 3T Incorrect Ownership Assignment (medium 5.9)
- [CVE-2021-42744](https://insights.sbomify.com/CVE-2021-42744/): Philips MRI 1.5T and 3T Information Exposure (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26262 and fix it if it is affected.

What it is: CVE-2021-26262 is a medium-severity missing authorization vulnerability in Philips MRI 1.5T, published on 19 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26262 in the wild and no public exploit code.

Affected product: Philips MRI 1.5T. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-26262/ (Markdown: https://insights.sbomify.com/CVE-2021-26262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-26262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-26262
- OSV: https://osv.dev/vulnerability/CVE-2021-26262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-26262/
Summaries are generated and may contain mistakes; the official description above is the record.