# CVE-2026-60060: Memory corruption in TTSSH2

> An attacker can trigger out-of-bounds memory access in TTSSH2, potentially leaking memory contents or causing application crashes during SSH connections.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:L/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 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-qcvw-2hm7-q2rp

## What is CVE-2026-60060?

CVE-2026-60060 is a medium-severity memory corruption vulnerability in TeraTerm Project TTSSH2, published on 17 Jul 2026. 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 Handling of Length Parameter Inconsistency (CWE-130) vulnerability exists in TTSSH2 plugin of Tera Term provided by TeraTerm Project. When Tera Term attempts to establish an SSH connection to a server set up by an attacker, out-of-bounds read/write may occur. As a result, the contents of adjacent memory regions may be transmitted to the server, and Tera Term may behave unexpected or terminate abnormally.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

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

## Is CVE-2026-60060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60060 is a medium-severity memory corruption vulnerability in TeraTerm Project TTSSH2, published on 17 Jul 2026. 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-2026-60060 in the wild and no public exploit code.

Affected product: TeraTerm Project TTSSH2. 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-60060/ (Markdown: https://insights.sbomify.com/CVE-2026-60060/index.md)
```

## Sources

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

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