Cyber Resilience

CVE-2026-60060

Published
17 July 2026
Modified
17 July 2026
CVSS Score v4 5.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-60060 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Github (inferred from references). Its CVSS base score is 5.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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.…

more

As a result, the contents of adjacent memory regions may be transmitted to the server, and Tera Term may behave unexpected or terminate abnormally.

CWE(s)
CWE-130

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1041 Exfiltration Over C2 Channel Exfiltration
Adversaries may steal data by exfiltrating it over an existing command and control channel.
attack.mitre.org →
Why these techniques?

OOB read in SSH client directly enables local memory contents to be sent to attacker-controlled server over the connection channel.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-5265Shared CWE-130
CVE-2024-20685Shared CWE-130
CVE-2026-33846Shared CWE-130
CVE-2024-35313Shared CWE-130
CVE-2024-39614Shared CWE-130
CVE-2026-33555Shared CWE-130
CVE-2026-25572Shared CWE-130
CVE-2023-5393Shared CWE-130
CVE-2024-38010Shared CWE-130
CVE-2023-53157Shared CWE-130

Affected Assets

Github
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for handling message lengths and data structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References