GHSA-4rh7-jwg9-m28m: Openssl encrypt Openssl-encrypt Accepts Refresh Tokens As Vulnerability

MODERATE
Share
CWE-598
Published
Advisory Summary

GHSA-4rh7-jwg9-m28m is a MODERATE openssl-encrypt accepts refresh tokens as vulnerability (CWE-598: Use of HTTP Request With Sensitive Query String) affecting Openssl encrypt libraries in the PyPI ecosystem. The issue involves openssl-encrypt accepts refresh tokens as url query parameters causing token leakage. Remediation is available by upgrading affected packages to version 1.4.0.

GHSA-4rh7-jwg9-m28m at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4rh7-jwg9-m28m
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-598: Use of HTTP Request With Sensitive Query String
Affected Product Openssl encrypt
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-4rh7-jwg9-m28m

To remediate this vulnerability, upgrade all affected Openssl encrypt dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openssl-encrypt fixed: 1.4.0 
pip install openssl-encrypt>=1.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show openssl-encrypt

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-4rh7-jwg9-m28m, inspect your installed packages using pip:

pip show openssl-encrypt

Analyze the terminal output to locate any version of Openssl encrypt in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.0), your application is affected.

Note: The pip show openssl-encrypt command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-598: Use of HTTP Request With Sensitive Query String, where the web application uses an http method to process a request, but the request includes sensitive information in the query string. In Openssl encrypt, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Refresh tokens are accepted as URL query parameters in the keyserver and telemetry server routes. ### Affected Code ```python # 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.

GHSA-4rh7-jwg9-m28m Affected Openssl encrypt Versions

1 component(s)
Fixed Versions:
1.4.0
Product / Package Ecosystem Affected Versions Fixed Version
openssl-encrypt
pypi/openssl-encrypt
PyPI
< 1.4.0
1.4.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-4rh7-jwg9-m28m
Security Fix Commit FIX COMMIT
https://github.com/jahlives/openssl_encrypt/commit/4b2adb05cde8a7ee03cdd271755da3b377c68011
Openssl encrypt Source Repository REPOSITORY
https://github.com/jahlives/openssl_encrypt

Frequently Asked Questions

What is GHSA-4rh7-jwg9-m28m?
GHSA-4rh7-jwg9-m28m is a security vulnerability in Openssl encrypt involving openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage under CWE-598: Use of HTTP Request With Sensitive Query String.
Which Openssl encrypt versions are affected?
Affected versions include releases prior to 1.4.0 across affected packages: openssl-encrypt.
What version fixes GHSA-4rh7-jwg9-m28m?
Upgrading to 1.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openssl-encrypt affected?
Yes, openssl-encrypt is affected in releases prior to 1.4.0. Upgrade your dependency to 1.4.0 or later.
What CWE is associated with GHSA-4rh7-jwg9-m28m?
GHSA-4rh7-jwg9-m28m is classified under CWE-598: Use of HTTP Request With Sensitive Query String (The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.).
How can I check PyPI dependencies for GHSA-4rh7-jwg9-m28m?
Run the dependency tree command: 'pip show openssl-encrypt'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4rh7-jwg9-m28m",
  "modified" : "2026-04-01T21:12:19Z",
  "published" : "2026-04-01T21:12:19Z",
  "aliases" : [ ],
  "summary" : "openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage",
  "details" : "### Summary\n\nRefresh tokens are accepted as URL query parameters in the keyserver and telemetry server routes.\n\n### Affected Code\n\n```python\n# openssl_encrypt_server/modules/keyserver/routes.py:214-215\n# openssl_encrypt_server/modules/telemetry/routes.py:90-91\nasync def refresh_token(\n    request: Request,\n    refresh_token: str = Query(..., description=\"Refresh token\")\n):\n```\n\n### Impact\n\nTokens in URL query parameters are exposed in:\n- Server access logs\n- Proxy/CDN logs\n- Browser history\n- HTTP Referer headers\n- Network monitoring tools\n\nThis creates significant token leakage risk.\n\n### Recommended Fix\n\n- Accept refresh tokens in the request body (POST) instead of query parameters\n- Use `Body(...)` instead of `Query(...)`\n\n### Fix\n\nFixed in commit `4b2adb0` on branch `releases/1.4.x` — moved refresh token from Query parameter to POST body via RefreshRequest Pydantic model.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "openssl-encrypt"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-4rh7-jwg9-m28m"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jahlives/openssl_encrypt/commit/4b2adb05cde8a7ee03cdd271755da3b377c68011"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jahlives/openssl_encrypt"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-598" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-01T21:12:19Z",
    "nvd_published_at" : null
  }
}