# CVE-2024-44141: The issue was addressed with improved checks.


- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2024
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-ghfq-rw9q-gx67

## What is CVE-2024-44141?

CVE-2024-44141 is a medium-severity vulnerability in Apple Macos, published on 24 Oct 2024. 

### Official description

The issue was addressed with improved checks. This issue is fixed in macOS Sonoma 14.6. A person with physical access to an unlocked Mac may be able to gain root code execution.

## Which versions are affected by CVE-2024-44141?

It affects 1 product.


Products: Apple Macos.

## How do I fix CVE-2024-44141?

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

## Is CVE-2024-44141 being exploited?

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

## Other vulnerabilities in Apple Macos

- [CVE-2026-65400](https://insights.sbomify.com/CVE-2026-65400/): Apple macOS Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2024-44146](https://insights.sbomify.com/CVE-2024-44146/): Security feature bypass in macOS (critical 10.0)
- [CVE-2024-44148](https://insights.sbomify.com/CVE-2024-44148/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-38586](https://insights.sbomify.com/CVE-2023-38586/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-40455](https://insights.sbomify.com/CVE-2023-40455/): Security feature bypass in macOS (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44141 and fix it if it is affected.

What it is: CVE-2024-44141 is a medium-severity vulnerability in Apple Macos, published on 24 Oct 2024. 
Exploitation: There is no known exploitation of CVE-2024-44141 in the wild and no public exploit code.

Affected product: Apple Macos. 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-2024-44141/ (Markdown: https://insights.sbomify.com/CVE-2024-44141/index.md)
```

## Sources

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

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