CVE-2020-2044: PAN-OS: Passwords may be logged in clear text while storing operational command (op command) history
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 8.1.16; 9.0.10; 9.1.3 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
An information exposure through log file vulnerability where an administrator's password or other sensitive information may be logged in cleartext while using the CLI in Palo Alto Networks PAN-OS software. The opcmdhistory.log file was introduced to track operational command (op-command) usage but did not mask all sensitive information. The opcmdhistory.log file is removed in PAN-OS 9.1 and later PAN-OS versions. Command usage is recorded, instead, in the req_stats.log file in PAN-OS 9.1 and later PAN-OS versions. This issue impacts: PAN-OS 8.1 versions earlier than PAN-OS 8.1.16; PAN-OS 9.0 versions earlier than PAN-OS 9.0.10; PAN-OS 9.1 versions earlier than PAN-OS 9.1.3.
- weakness
- CWE-532 Information Exposure Through Log Files
- affected
- Palo Alto Networks PAN-OS
- published ranges
- paloaltonetworks pan-os >= 8.0.0 <= 8.0.20; paloaltonetworks pan-os >= 8.1.0 < 8.1.16; paloaltonetworks pan-os >= 9.0.0 < 9.0.10; paloaltonetworks pan-os >= 9.1.0 < 9.1.3
- fixed in
- 8.1.16; 9.0.10; 9.1.3
- severity
- 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- assigned by
- palo_alto
- published
- 2020-09-09
check us security.paloaltonetworks.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Apr 2021 | 0.00416 | |
| 6 Jan 2022 | 0.0184 | |
| 4 Feb 2022 | 0.01404 | |
| 1 Apr 2022 | 0.00885 | |
| 7 Mar 2023 | 0.00044 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.00228 | scoring model v2025.03.14 |
| 21 Nov 2025 | 0.00228 | |
| 27 Dec 2025 | 0.00164 | |
| 28 Dec 2025 | 0.00228 | |
| 15 Jun 2026 | 0.00732 | scoring model v2026.06.15 |
18 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 8.1.16; 9.0.10; 9.1.3. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2020-2044', '2026-10-31T23:59:59.999999Z', now());