# CVE-2026-44279: Information disclosure in FortiTokenAndroid

> An attacker can disclose sensitive information via an exported Content Provider URI in the FortiToken Android application.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-6xw2-cp28-pgvr

## What is CVE-2026-44279?

CVE-2026-44279 is a medium-severity vulnerability in Fortinet FortiTokenAndroid, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper export of android application components vulnerability in Fortinet FortiTokenAndroid 6.2 all versions, FortiTokenAndroid 6.1 all versions, FortiTokenAndroid 5.2 all versions may allow attacker to disclose information via an exported Content Provider URI.

Weakness: CWE-926 (Improper Export of Android Application Components)

## Which versions are affected by CVE-2026-44279?

It affects 1 product.


Products: Fortinet Fortitoken Mobile.

## How do I fix CVE-2026-44279?

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

## Is CVE-2026-44279 being exploited?

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

## Other vulnerabilities in Fortinet FortiTokenAndroid

- [CVE-2021-22131](https://insights.sbomify.com/CVE-2021-22131/): Weak cryptography in Fortinet FortiTokenAndroid, Fortinet FortiTokeniOS, Fortinet FortiTokenWinApp (medium 6.4)
- [CVE-2021-44166](https://insights.sbomify.com/CVE-2021-44166/): Auth bypass in Fortinet FortiTokenAndroid (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44279 and fix it if it is affected.

What it is: CVE-2026-44279 is a medium-severity vulnerability in Fortinet FortiTokenAndroid, published on 12 May 2026. 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-2026-44279 in the wild and no public exploit code.

Affected product: Fortinet FortiTokenAndroid. 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-2026-44279/ (Markdown: https://insights.sbomify.com/CVE-2026-44279/index.md)
```

## Sources

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

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