# CVE-2026-59776: Weak cryptography in FeliCa IC chips

> Attackers can read or tamper with data on FeliCa IC chips due to a missing cryptographic step in the hardware design.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-4jgm-gw57-4jwf

## What is CVE-2026-59776?

CVE-2026-59776 is a high-severity vulnerability in Sony Corporation FeliCa IC chips, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Missing Cryptographic Step (CWE-325) vulnerability exists in certain FeliCa IC chips shipped in or before 2017. If the vulnerability is exploited, information stored in the IC chip may be read or tampered with.

Weakness: CWE-325 (Missing Cryptographic Step)

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


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

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

## Is CVE-2026-59776 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59776 is a high-severity vulnerability in Sony Corporation FeliCa IC chips, published on 21 Jul 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-59776 in the wild and no public exploit code.

Affected product: Sony Corporation FeliCa IC chips. 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-59776/ (Markdown: https://insights.sbomify.com/CVE-2026-59776/index.md)
```

## Sources

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

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