Advisory

GHSA-4rh7-jwg9-m28m

Also known as: CVE-2026-74880, PYSEC-2026-3759

Summary

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

Details

Summary

Refresh tokens are accepted as URL query parameters in the keyserver and telemetry server routes.

Affected Code

# openssl_encrypt_server/modules/keyserver/routes.py:214-215
# openssl_encrypt_server/modules/telemetry/routes.py:90-91
async def refresh_token(
    request: Request,
    refresh_token: str = Query(..., description="Refresh token")
):

Impact

Tokens in URL query parameters are exposed in:

  • Server access logs
  • Proxy/CDN logs
  • Browser history
  • HTTP Referer headers
  • Network monitoring tools

This creates significant token leakage risk.

Recommended Fix

  • Accept refresh tokens in the request body (POST) instead of query parameters
  • Use Body(...) instead of Query(...)

Fix

Fixed in commit 4b2adb0 on branch releases/1.4.x — moved refresh token from Query parameter to POST body via RefreshRequest Pydantic model.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-01 21:12 UTC
Modified
2026-09-02 09:10 UTC

Affected packages and fixes

openssl-encrypt

PyPI · All systems

Affected

  • introduced 0, fixed 1.4.0 (ecosystem)

Fixed versions

1.4.0

Fix

  • Fixed version 1.4.0
    pip install --upgrade openssl-encrypt==1.4.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences