CVE-2026-81705: openssl-encrypt before 1.4.9 Password Cleartext Leak via Debug

Published Aug 27, 2026
·
Updated

openssl-encrypt before 1.4.9 fails to redact the file password in its --debug argv dump when the password is supplied via bundled short-option spellings (e.g. -apHunter2) or abbreviated long-option spellings (e.g. --passw). The sanitizer only recognized exact option names, --option=value forms, and tokens starting with -p, so these spellings bypass the redaction chokepoint and the cleartext password is written to stderr. Anyone with access to that output (terminal scrollback, merged 2>&1 output, CI job logs, or the GUI's persistent debug log) can recover the password.

Affected Software

1 affected component
OpenSSL openssl-encrypt<1.4.9

Event History

Aug 27, 2026
CVE Published
via MITRE·02:51 PM
Data Sourced
via MITRE·02:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this leak?

Users of openssl-encrypt before 1.4.9 are exposed when they enable --debug and provide a file password using bundled short-option spellings such as -apHunter2 or abbreviated long-option spellings such as --passw. Anyone able to view the resulting stderr, including CI log readers and users with access to persistent GUI debug logs, can recover the password.

2

Does exploitation require access to the affected system or the ability to run the tool?

The password is written to stderr during the affected debug invocation. An attacker needs access to the generated output, such as terminal scrollback, merged 2>&1 output, CI job logs, or the GUI's persistent debug log; the advisory does not describe a need to execute the tool themselves.

3

What can be done if upgrading is not immediately possible?

Avoid using --debug when supplying file passwords, particularly with bundled short options or abbreviated long options. Treat existing debug output and logs from affected invocations as exposed, restrict access where possible, and change any passwords that may have been recorded.

4

How can I determine whether passwords may already have leaked?

Review terminal scrollback, redirected or merged stderr output, CI job logs, and persistent GUI debug logs for openssl-encrypt debug invocations before 1.4.9. Focus on runs where passwords were supplied using bundled short-option or abbreviated long-option spellings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203