VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ryanbekhen/nanoproxy: vulnerability history, versions and safety

github.com/ryanbekhen/nanoproxy is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 90 releases, first recorded in Dec 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 H1 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/ryanbekhen/nanoproxy vulnerabilities

Vulert verdict on github.com/ryanbekhen/nanoproxy v0.17.7 i

Updated on 23 Oct 2026

Action needed: v0.17.7 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 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • 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 v0.17.7 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 13 Dec 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 25 i
  • Last release 2 months ago i
  • Licence MIT 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/ryanbekhen/nanoproxy, 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
v0.17.7 22 Aug 2026 H1 U1 MIT Yes Details →
v0.17.6 22 Aug 2026 H1 U1 MIT Yes Details →
v0.17.5 22 Aug 2026 H1 U1 MIT Yes Details →
v0.17.4 17 Jul 2026 H1 U1 MIT Yes Details →
v0.17.3 17 May 2026 H1 U1 MIT Yes Details →
v0.17.2 11 May 2026 H1 U1 MIT Yes Details →
v0.17.1 03 May 2026 H1 U1 MIT Yes Details →
v0.17.0 02 May 2026 H1 U1 MIT Yes Details →
v0.16.0 26 Mar 2026 H1 U1 MIT Yes Details →
v0.15.7 24 Mar 2026 H1 U1 MIT Yes Details →
v0.15.6 19 Feb 2026 H1 U1 MIT Yes Details →
v0.15.5 07 Dec 2025 H1 U1 MIT Yes Details →
v0.15.4 05 Apr 2025 H1 U1 MIT Yes Details →
v0.15.3 25 Jan 2025 H1 U1 MIT Yes Details →
v0.15.2-0.20250123204907-1684121827d9 23 Jan 2025 H1 U1 MIT Yes Details →
v0.15.2 23 Jan 2025 H1 U1 MIT Yes Details →
v0.15.1 13 Dec 2024 H1 U1 MIT Yes Details →
v0.15.0 12 Dec 2024 H1 U1 MIT Yes Details →
v0.14.2-0.20241209152013-cca87ae30b35 09 Dec 2024 H1 U1 MIT Yes Details →
v0.14.2-0.20241208104232-ff6018a43b70 08 Dec 2024 H1 U1 MIT Yes Details →
v0.14.2-0.20241208022938-bd5bb082c194 08 Dec 2024 H1 U1 MIT Yes Details →
v0.14.1 08 Dec 2024 H1 U1 MIT Yes Details →
v0.13.3-0.20241208004231-3f0bac57bd77 08 Dec 2024 H1 U1 MIT Yes Details →
v0.14.0 08 Dec 2024 H1 U1 MIT Yes Details →
v0.13.3-0.20241207162941-d56db163a007 07 Dec 2024 H1 U1 MIT Yes Details →
v0.13.2 07 Dec 2024 H1 U1 MIT Yes Details →
v0.13.2-0.20240822133009-5d9a53ffd04b 22 Aug 2024 H1 U1 MIT Yes Details →
v0.13.2-0.20240529133226-cc629a9353d3 29 May 2024 H1 U1 MIT Yes Details →
v0.13.2-0.20240523112112-a632694d16c5 23 May 2024 H1 U1 MIT Yes Details →
v0.13.2-0.20240523093932-6d62a2e743ba 23 May 2024 H1 U1 MIT Yes Details →
v0.13.1 23 May 2024 H1 U1 MIT Yes Details →
v0.13.0 23 May 2024 H1 U1 MIT Yes Details →
v0.12.10-0.20240308070808-9999fbdc7682 08 Mar 2024 H1 U1 MIT Yes Details →
v0.12.10-0.20240215074501-062f1c9ce38f 15 Feb 2024 H1 U1 MIT Yes Details →
v0.12.9 15 Feb 2024 H1 U1 MIT Yes Details →
v0.12.8 12 Feb 2024 H1 U1 MIT Yes Details →
v0.12.7 28 Dec 2023 H1 U1 MIT Yes Details →
v0.12.7-0.20231228192622-c162ca131143 28 Dec 2023 H1 U1 MIT Yes Details →
v0.12.6 07 Dec 2023 H1 U1 MIT Yes Details →
v0.12.6-0.20231207124857-567bc2bdc64f 07 Dec 2023 H1 U1 MIT Yes Details →
v0.12.5 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.5-0.20231130200954-24c9a8ff03b1 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.4 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.3 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.2 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.2-0.20231130193803-0b852ba822f2 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.1 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.1-0.20231130153350-e3a5941b3e60 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.0 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.4-next.0.20231130100536-eaedaee855b6 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.5-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.12.0 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.3-next.0.20231130100007-e244e0e07ba0 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.4-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.2-next.0.20231130095518-a37b22a0102c 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.3-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.1-next.0.20231130094239-870342382397 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.2-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.0-next.0.20231130093725-c72587e6480d 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.1-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.10.1-0.20231130055022-b41988874798 30 Nov 2023 H1 U1 MIT Yes Details →
v0.11.0-next 30 Nov 2023 H1 U1 MIT Yes Details →
v0.10.1-0.20231127093043-6c70a8622881 27 Nov 2023 H1 U1 MIT Yes Details →
v0.10.0 27 Nov 2023 H1 U1 MIT Yes Details →
v0.9.0 27 Nov 2023 H1 U1 MIT Yes Details →
v0.8.3 27 Nov 2023 H1 U1 MIT Yes Details →
v0.8.2 26 Nov 2023 H1 U1 MIT Yes Details →
v0.8.1 26 Nov 2023 H1 U1 MIT Yes Details →
v0.8.0 26 Nov 2023 H1 U1 MIT Yes Details →
v0.7.0 23 Nov 2023 H1 U1 MIT Yes Details →
v0.6.0 24 Sep 2023 H1 U1 MIT Yes Details →
v0.5.1 24 Sep 2023 H1 U1 MIT Yes Details →
v0.5.0 24 Sep 2023 H1 U1 MIT Yes Details →
v0.4.1 21 Sep 2023 H1 U1 MIT Yes Details →
v0.4.1-0.20230921215903-f341795c70aa 21 Sep 2023 H1 U1 MIT Yes Details →
v0.4.0 21 Sep 2023 H1 U1 MIT Yes Details →
v0.3.0 21 Sep 2023 H1 U1 MIT Yes Details →
v0.2.6 19 Sep 2023 H1 U1 MIT Yes Details →
v0.2.6-0.20230919062648-36e212b35519 19 Sep 2023 H1 U1 MIT Yes Details →
v0.2.5 18 Sep 2023 H1 U1 MIT Yes Details →
v0.2.4 18 Sep 2023 H1 U1 MIT Yes Details →
v0.2.3 18 Sep 2023 H1 U1 MIT Yes Details →
v0.2.2 18 Sep 2023 H1 U1 MIT Yes Details →
v0.2.2-0.20230831210726-e3e287e190c4 31 Aug 2023 H1 U1 MIT Yes Details →
v0.2.1 31 Aug 2023 H1 U1 MIT Yes Details →
v0.2.1-0.20230831152421-d516ab45cd77 31 Aug 2023 H1 U1 MIT Yes Details →
v0.2.0 29 Aug 2023 H1 U1 MIT Yes Details →
v0.1.1 28 Aug 2023 H1 U1 MIT Yes Details →
v0.1.0 28 Aug 2023 H1 U1 MIT Yes Details →
v0.0.1 27 Aug 2023 H1 U1 MIT Yes Details →

All 90 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/ryanbekhen/nanoproxy

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in NanoProxy Due to Outdated golang.org/x/crypto Dependency N/A high 0.15.0 12 Dec 2024
Outdated Dependency Vulnerability in NanoProxy: Potential Security Risks N/A unrated 0.15.0 13 Dec 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/ryanbekhen/nanoproxy

Is github.com/ryanbekhen/nanoproxy safe to use?

Vulert records 2 vulnerabilities for github.com/ryanbekhen/nanoproxy in Go: 0 critical, 1 high, 0 medium and 0 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/ryanbekhen/nanoproxy's Vulert package health score?

Vulert scores github.com/ryanbekhen/nanoproxy 73/100, which reads as in good shape. 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/ryanbekhen/nanoproxy affected?

Yes. v0.17.7, 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/ryanbekhen/nanoproxy should I use?

v0.17.7 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/ryanbekhen/nanoproxy have?

2 vulnerabilities are recorded for github.com/ryanbekhen/nanoproxy in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 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/ryanbekhen/nanoproxy vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ryanbekhen/nanoproxy in the last 12 months, and the oldest entry in this database dates to 12 Dec 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/ryanbekhen/nanoproxy 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/ryanbekhen/nanoproxy for upcoming vulnerabilities?

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