# CVE-2025-60022: Security feature bypass in 'デジラアプリ' App for iOS

> Improper certificate validation in the Digira iOS app allows attackers to intercept and modify encrypted communications via man-in-the-middle attacks.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-5xcx-xjwc-j24x

## What is CVE-2025-60022?

CVE-2025-60022 is a low-severity vulnerability in KDDI CORPORATION 'デジラアプリ' App for iOS, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper certificate validation vulnerability exists in 'デジラアプリ' App for iOS prior to ver.80.10.00. If this vulnerability is exploited, a man-in-the-middle attack may allow an attacker to eavesdrop on and/or tamper with an encrypted communication.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2025-60022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60022 is a low-severity vulnerability in KDDI CORPORATION 'デジラアプリ' App for iOS, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-60022 in the wild and no public exploit code.

Affected product: KDDI CORPORATION 'デジラアプリ' App for iOS. 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-60022/ (Markdown: https://insights.sbomify.com/CVE-2025-60022/index.md)
```

## Sources

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

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