# CVE-2024-49056: Airlift.microsoft.com Elevation of Privilege Vulnerability

> An authorized attacker can elevate privileges on Microsoft Airlift by exploiting an authentication bypass involving assumed-immutable data.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-3g36-jm7h-4mqf

## What is CVE-2024-49056?

CVE-2024-49056 is a high-severity authentication bypass vulnerability in airlift.microsoft.com, published on 12 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Authentication bypass by assumed-immutable data on airlift.microsoft.com allows an authorized attacker to elevate privileges over a network.

Weakness: CWE-302 (Authentication Bypass by Assumed-Immutable Data)

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

It affects 1 product.


Products: Microsoft Airlift Microsoft Com.

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

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

## Is CVE-2024-49056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49056 is a high-severity authentication bypass vulnerability in airlift.microsoft.com, published on 12 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-49056 in the wild and no public exploit code.

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

## Sources

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

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