# CVE-2022-46081: Information disclosure in n/a

> Terminating a LiveTrack session in Garmin Connect fails to stop the API from exposing private personal information, posing a privacy risk to users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-4q2q-9g24-gmxw

## What is CVE-2022-46081?

CVE-2022-46081 is a high-severity vulnerability in n/a, published on 4 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Garmin Connect 4.61, terminating a LiveTrack session wouldn't prevent the LiveTrack API from continued exposure of private personal information. NOTE: this is disputed by the vendor because the LiveTrack API service is not a customer-controlled product.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-46081?

It affects 1 product.


Products: Garmin Connect.

## How do I fix CVE-2022-46081?

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

## Is CVE-2022-46081 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46081 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46081 and fix it if it is affected.

What it is: CVE-2022-46081 is a high-severity vulnerability in n/a, published on 4 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46081 exists.

Affected product: n/a. 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-2022-46081/ (Markdown: https://insights.sbomify.com/CVE-2022-46081/index.md)
```

## Sources

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

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