Search
Find a vulnerability
Search criteria
ⓘ
Use this form to refine search results.
Full-text search supports keyword queries with ranking and filtering.
You can combine vendor, product, and sources to narrow results.
Enable “Apply ordering” to sort by date instead of relevance.
Related vulnerabilities
PYSEC-2026-3791
Vulnerability from pysec - Published: 2026-08-27 17:20 - Updated: 2026-09-03 10:37
VLAI
Details
openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 advertise a portable USB workspace as an 'Encrypted USB Workspace' with AES-256-GCM encryption and write a marker declaring the workspace encrypted, but the workspace directory is actually stored in cleartext and the derived encryption key is never applied to it. A user who trusts the branding and places files in the workspace leaves them unencrypted on the removable media, so an attacker with physical access to the media can read the sensitive files. Fixed in 1.4.9, which seals the workspace into an authenticated AES-256-GCM vault.
Severity
Impacted products
| Name | purl | openssl-encrypt | pkg:pypi/openssl-encrypt |
|---|
Aliases
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "openssl-encrypt",
"purl": "pkg:pypi/openssl-encrypt"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.2.2",
"0.2.3",
"0.2.4",
"0.2.5",
"0.2.6",
"0.3.0",
"0.3.1",
"0.3.2",
"0.3.3",
"0.4.0",
"0.4.1",
"0.4.2",
"0.4.3",
"0.4.4",
"0.5.0",
"0.5.1",
"0.5.3",
"0.6.0rc1",
"0.7.0rc2",
"0.7.1",
"0.7.2",
"0.8.0",
"0.8.1",
"0.8.2",
"0.9.2",
"1.0.0",
"1.0.1",
"1.0.2",
"1.0.3",
"1.1.0",
"1.2.0",
"1.2.1",
"1.3.0",
"1.3.1",
"1.3.2",
"1.3.3",
"1.3.4",
"1.3.5",
"1.4.0",
"1.4.0b3",
"1.4.0b4",
"1.4.0b5",
"1.4.0b6",
"1.4.0b7",
"1.4.0b8",
"1.4.1",
"1.4.1rc2",
"1.4.2",
"1.4.4",
"1.4.5",
"1.4.6",
"1.4.7",
"1.4.8"
]
}
],
"aliases": [
"CVE-2026-81681",
"GHSA-2jv6-qqfm-m46m"
],
"details": "openssl_encrypt (pip package openssl-encrypt) versions \u003c= 1.4.8 advertise a portable USB workspace as an \u0027Encrypted USB Workspace\u0027 with AES-256-GCM encryption and write a marker declaring the workspace encrypted, but the workspace directory is actually stored in cleartext and the derived encryption key is never applied to it. A user who trusts the branding and places files in the workspace leaves them unencrypted on the removable media, so an attacker with physical access to the media can read the sensitive files. Fixed in 1.4.9, which seals the workspace into an authenticated AES-256-GCM vault.",
"id": "PYSEC-2026-3791",
"modified": "2026-09-03T10:37:17.886108Z",
"published": "2026-08-27T17:20:57.453Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-2jv6-qqfm-m46m"
},
{
"type": "ADVISORY",
"url": "https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-false-encryption-via-cleartext-storage"
}
],
"severity": [
{
"score": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}