VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cea-hpc/sshproxy: vulnerability history, versions and safety

github.com/cea-hpc/sshproxy is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 36 releases, from May 2024 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/cea-hpc/sshproxy vulnerabilities

Vulert verdict on github.com/cea-hpc/sshproxy v1.6.3 i

Updated on 23 Oct 2026

Action needed: v1.6.3 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.6.3 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Jun 2024 i
  • Highest CVSS 3.5 i
  • With no published fix 0 i
  • Stars 116 i
  • OpenSSF scorecard 2/10 i
  • Last release 29 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/cea-hpc/sshproxy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.6.3-0.20261008134858-d1483a4638ac 08 Oct 2026 L1 U1 — Yes Details →
v1.6.3-0.20260901092008-c99fb6776d48 01 Sep 2026 L1 U1 — Yes Details →
v1.6.3-0.20260710093316-72398596cf8f 10 Jul 2026 L1 U1 — Yes Details →
v1.6.3-0.20241129154455-3e69ffc74e56 29 Nov 2024 L1 U1 — Yes Details →
v1.6.3 14 May 2024 L1 U1 — Yes Details →
v1.6.3-0.20240315082948-d7a8cc90e746 15 Mar 2024 L1 U1 — Yes Details →
v1.6.2 24 Jan 2024 L1 U1 — Yes Details →
v1.6.1 27 Nov 2023 L1 U1 — Yes Details →
v1.6.1-0.20231127093417-2d0609c0d31f 27 Nov 2023 L1 U1 — Yes Details →
v1.6.0 10 Oct 2023 L1 U1 — Yes Details →
v1.5.2 08 Sep 2023 L1 U1 — Yes Details →
v1.5.1 22 Mar 2022 L1 U1 — Yes Details →
v1.5.0 26 Oct 2021 L1 U1 — Yes Details →
v1.4.0 16 Aug 2021 L1 U1 — Yes Details →
v1.3.8 28 Jul 2021 L1 U1 — Yes Details →
v1.3.7 06 Jul 2021 L1 U1 — Yes Details →
v1.3.6 09 Apr 2021 L1 U1 — Yes Details →
v1.3.5 05 Mar 2021 L1 U1 — Yes Details →
v1.3.4 26 Jan 2021 L1 U1 — Yes Details →
v1.3.3 05 Oct 2020 L1 U1 — Yes Details →
v1.3.2 28 Sep 2020 L1 U1 — Yes Details →
v1.3.1 23 Sep 2020 L1 U1 — Yes Details →
v1.3.0 05 Aug 2020 L1 U1 — Yes Details →
v1.2.0 30 Apr 2020 L1 U1 — Yes Details →
v1.1.0 20 Mar 2020 L1 U1 — Yes Details →
v1.0.0 06 Jun 2019 L1 U1 — Yes Details →
v0.4.5 11 Jan 2018 L1 U1 — Yes Details →
v0.4.4 12 Sep 2016 L1 U1 — Yes Details →
v0.4.3 13 Jul 2016 L1 U1 — Yes Details →
v0.4.2 25 Apr 2016 L1 U1 — Yes Details →
v0.4.1 08 Dec 2015 L1 U1 — Yes Details →
v0.4.0 23 Nov 2015 L1 U1 — Yes Details →
v0.3.1 24 Jun 2015 L1 U1 — Yes Details →
v0.3.0 25 Mar 2015 L1 U1 — Yes Details →
v0.2.0 02 Mar 2015 L1 U1 — Yes Details →
v0.1.0 13 Feb 2015 L1 U1 — Yes Details →

All 36 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/cea-hpc/sshproxy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
SSHProxy Vulnerability: SSH Option Injection 3.5 low 1.6.3 14 May 2024
CVE-2024-34713: SSH Option Injection in github.com/cea-hpc/sshproxy N/A unrated 1.6.3 04 Jun 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/cea-hpc/sshproxy

Is github.com/cea-hpc/sshproxy safe to use?

Vulert records 2 vulnerabilities for github.com/cea-hpc/sshproxy in Go: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/cea-hpc/sshproxy's Vulert package health score?

Vulert scores github.com/cea-hpc/sshproxy 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/cea-hpc/sshproxy affected?

Yes. v1.6.3, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/cea-hpc/sshproxy should I use?

v1.6.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/cea-hpc/sshproxy have?

2 vulnerabilities are recorded for github.com/cea-hpc/sshproxy in the Go ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/cea-hpc/sshproxy vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cea-hpc/sshproxy in the last 12 months, and the oldest entry in this database dates to 14 May 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/cea-hpc/sshproxy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/cea-hpc/sshproxy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cea-hpc/sshproxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.