# CVE-2026-73281: In ssh-agent in OpenSSH before 10.5, some operations can occur remotely but were intended to occur only locally…

Source: https://junglewise.ai/threats/cve-2026-73281-in-ssh-agent-in-openssh-before-10-5-some-operations-can-occur  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-11  
License: CC BY 4.0 with a link back

CVE-2026-73281 · Severity: low · CVSS 3.5 · Published 2026-08-11

In ssh-agent in OpenSSH before 10.5, some operations can occur remotely but were intended to occur only locally, including operations that add tokens or use keys. This is caused by misinteraction between agent locking and the session-bind@openssh.com extension.

Technologies: [OpenBSD Openssh](https://junglewise.ai/threats/technologies/openssh). Vendors: [OpenBSD](https://junglewise.ai/threats/vendors/openbsd).

## Quick answers

**Is CVE-2026-73281 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-73281 being exploited in the wild.

**How severe is CVE-2026-73281?** Low severity, with a CVSS score of 3.5, published 11 August 2026.

**Which products and versions are affected?** OpenBSD Openssh. The advisory does not name versions.

**Is there a fix for CVE-2026-73281?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-73281?** Check whether you run OpenBSD Openssh. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- OpenBSD Openssh

## Related threats

- [OpenSSH password authentication bypass on musl libc without PAM](https://junglewise.ai/threats/cve-2026-123158-sshd-in-openssh-before-10-6p2-on-linux-when-musl-libc-is-used)
- [In sshd in OpenSSH before 10.5, the restrict keyword (in authorized_keys) was supposed to be applicable to tunnel forwarding but was not.](https://junglewise.ai/threats/cve-2026-73283-in-sshd-in-openssh-before-10-5-the-restrict-keyword-in-authorized)
- [In ssh in OpenSSH before 10.5, a use-after-free for realloc data can occur if a certain pair of remote-forwarding operations are concurrent.](https://junglewise.ai/threats/cve-2026-73282-in-ssh-in-openssh-before-10-5-a-use-after-free-for-realloc-data)
- [OpenSSH use-after-free in ssh client during key re-exchange](https://junglewise.ai/threats/cve-2026-60002-openssh-use-after-free-in-ssh-client-during-key-re-exchange)
- [OpenSSH sshd failure to enforce minimum authentication delay](https://junglewise.ai/threats/cve-2026-60001-openssh-sshd-failure-to-enforce-minimum-authentication-delay)