openssl-encrypt has CORS wildcard with allow_credentials=True in standalone servers
Published Aug 17, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
openssl-encrypt has CORS wildcard with allow_credentials=True in standalone servers
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Both standalone servers configure CORS with alloworigins=[""], allowcredentials=True, allowmethods=[""], and allowheaders=[""].
Potential 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- VulnCheck Advisory: openssl_encrypt before 1.4.0 CORS Misconfiguration via Wildcard Origins ↗
Record history
Published Aug 17, 2026 · Last refreshed Nov 3, 2026