# CVE-2025-48219: Information disclosure in O2

> O2 UK subscribers can leak other users' Cell IDs via SIP headers, potentially revealing their physical location.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-7rcm-4jcj-r4q6

## What is CVE-2025-48219?

CVE-2025-48219 is a low-severity vulnerability in O2, published on 18 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

O2 UK before 2025-05-19 allows subscribers to determine the Cell ID of other subscribers by initiating an IMS (IP Multimedia Subsystem) call and then reading the utran-cell-id-3gpp field of a Cellular-Network-Info SIP header, aka an ECI (E-UTRAN Cell Identity) leak. The Cell ID might be usable to identify a cell location via crowdsourced data, and might correspond to a small physical area (e.g., if the called party is in a city centre). Removal of the Cellular-Network-Info header is mentioned in section 4.4.19 of ETSI TS 124 229.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-48219?


## How do I fix CVE-2025-48219?

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

## Is CVE-2025-48219 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48219 and fix it if it is affected.

What it is: CVE-2025-48219 is a low-severity vulnerability in O2, published on 18 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48219 in the wild and no public exploit code.

Affected product: O2. 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-2025-48219/ (Markdown: https://insights.sbomify.com/CVE-2025-48219/index.md)
```

## Sources

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

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