Potential Vulnerabilities Due to Outdated golang.org/x/crypto Dependency in NanoProxy

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

A security issue was identified in the NanoProxy project related to the golang.org/x/crypto dependency. The project was using an outdated version of this dependency, which potentially exposed the system to security vulnerabilities that have been addressed in subsequent updates. Impact: The specific vulnerabilities in the outdated version of golang.org/x/crypto could include authorization bypasses, data breaches, or other security risks. These vulnerabilities can be exploited by attackers to compromise the integrity, confidentiality, or availability of the system. Resolution: The issue has been fixed in NanoProxy by upgrading the golang.org/x/crypto dependency to version 0.31.0. Users are strongly encouraged to update their instances of NanoProxy to include this fix and ensure they are using the latest secure version of all dependencies. Fixed Version: golang.org/x/crypto upgraded to version 0.31.0.

Published by the source

12 Dec 2024, 19:20 UTC

Last modified by the source

13 Dec 2024, 21:46 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7prj-hgx4-2xc3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7prj-hgx4-2xc3

Advisory: Potential Vulnerabilities Due to Outdated golang.org/x/crypto Dependency in NanoProxy
IDs: GHSA-7prj-hgx4-2xc3
Record: https://patchnext.com/advisories/ghsa-7prj-hgx4-2xc3 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ryanbekhen/nanoproxy 0.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ryanbekhen/nanoproxy: affected < 0.15.0; fixed in 0.15.0

## Suggested inspection (read-only)
- Go github.com/ryanbekhen/nanoproxy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ryanbekhen/nanoproxy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7prj-hgx4-2xc3 (GitHub-reviewed advisory GHSA-7prj-hgx4-2xc3 lists affected ranges: Go github.com/ryanbekhen/nanoproxy >=0 <0.15.0)

Commands are suggestions: review each one before running it.