Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

blinksocks has weak encryption algorithms

CVE-2023-50481GHSA-pqj5-37xf-x5gc

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm blinksocks

    Affected
    <= 3.3.8
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2023-50481: 0.27% estimated exploitation activity in the next 30 days; percentile 19.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

An issue was discovered in blinksocks version 3.3.8, allows remote attackers to obtain sensitive information via weak encryption algorithms in the component /presets/ssr-auth-chain.js.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-pqj5-37xf-x5gc

  2. Revision 1 · created ·

    Published from osv record GHSA-pqj5-37xf-x5gc

Agent brief

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

# Patch Next advisory brief: CVE-2023-50481

Advisory: blinksocks has weak encryption algorithms
IDs: CVE-2023-50481, GHSA-pqj5-37xf-x5gc
Record: https://patchnext.com/advisories/cve-2023-50481 (revision 2, source checked 26 Oct 2026, 12:30 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm blinksocks: affected <= 3.3.8

## Suggested inspection (read-only)
- `npm ls blinksocks --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on blinksocks.
- 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://osv.dev/vulnerability/GHSA-pqj5-37xf-x5gc (OSV record GHSA-pqj5-37xf-x5gc lists affected ranges: npm blinksocks >=0 <=3.3.8)
- Verified: https://github.com/advisories/GHSA-pqj5-37xf-x5gc (GitHub-reviewed advisory GHSA-pqj5-37xf-x5gc lists affected ranges: npm blinksocks >=0 <=3.3.8)

Commands are suggestions: review each one before running it.

Loading voting…