Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4rh7-jwg9-m28m

openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage

CVSS 9.3 CriticalCriticalEPSS 0.0056 · 46th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 1 Apr 2026, 21:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
openssl-encryptPyPI<1.4.01.4.0
Identifiers
GHSA-4rh7-jwg9-m28m · CVE-2026-74880 · PYSEC-2026-3759
Weakness (CWE)
CWE-598
Tags
Published
1 Apr 2026
Updated
2 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of openssl-encrypt before 1.4.0 accept refresh tokens as URL query parameters on the keyserver and telemetry server routes, so tokens can end up in server access logs, proxy or CDN logs, browser history, HTTP Referer headers, and network monitoring tools. The source does not say what an attacker must already have access to in order to read those logs. Upgrade to openssl-encrypt 1.4.0, which moves the refresh token into the POST request body.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0056, the 46th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:38 UTC First seen by agentprime
  2. 31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.