openssl-encrypt
Affected
- introduced
0, fixed1.4.0(ecosystem)
Fixed versions
1.4.0
Fix
- Fixed version
1.4.0pip install --upgrade openssl-encrypt==1.4.0
Advisory
Also known as: CVE-2026-74881, PYSEC-2026-3977
openssl-encrypt has CORS wildcard with allow_credentials=True in standalone servers
Summary
Both standalone servers configure CORS with allow_origins=["*"], allow_credentials=True, allow_methods=["*"], and allow_headers=["*"].
Affected Code
# server/key-server/app/main.py:86-92
# server/telemetry-server/app/main.py:23-29
app.add_middleware(
CORSMiddleware,
allow_origins=settings.cors_origins, # defaults to ["*"]
allow_credentials=True,
allow_methods=["*"],
allow_headers=["*"],
)
The docker-compose file (openssl_encrypt_server/docker-compose.yml:75) also defaults CORS_ORIGINS to *, and .env.example ships with CORS_ORIGINS=*.
Impact
This is the most permissive CORS configuration possible, allowing any website to make fully credentialed cross-origin requests to the API. An attacker's website could make authenticated API calls on behalf of any user who visits it.
Recommended Fix
allow_origins=["*"] with allow_credentials=True.env.example with placeholder domains instead of *Fix
Fixed in commit 809416b on branch releases/1.4.x — changed CORS default from ["*"] to [] in both key-server and telemetry-server; added validation rejecting wildcard when debug=False.
Medium Basis: The source's own band: MODERATE
0, fixed 1.4.0 (ecosystem)1.4.0
1.4.0pip install --upgrade openssl-encrypt==1.4.0Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0