CVE-2022-26306 | Execution of Untrusted Macros Due to Improper Certificate Validation

LibreOffice supports the storage of passwords for web connections in the user’s configuration database. The stored passwords are encrypted with a single master key provided by the user. A flaw in LibreOffice existed where the required initialization vector for encryption was always the same which weakens the security of the encryption making them vulnerable if an attacker has access to the user's configuration data. This issue affects: The Document Foundation LibreOffice 7.2 versions prior to 7.2.7; 7.3 versions prior to 7.3.1.

Published: 2022-07-25 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-26306 is rated Moderate Risk (52.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-26306

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-29 0.46% 0.45% -0.01%
2 2026-05-22 0.36% 0.46% +0.10%
3 2026-01-01 — 0.36% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26306

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2022-26306

OS Trackers for CVE-2022-26306

vendor priority summary link
alpine high CVE-2022-26306: 1 source package rows (libreoffice); 11 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 4. https://security.alpinelinux.org/vuln/CVE-2022-26306
debian not yet assigned CVE-2022-26306 not yet assigned priority: Debian including 1 source packages (libreoffice), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-26306
redhat medium — https://access.redhat.com/security/cve/CVE-2022-26306
suse low — https://www.suse.com/security/cve/CVE-2022-26306/
ubuntu medium CVE-2022-26306 medium priority: Ubuntu including 1 source packages (libreoffice), 8 status rows across 8 suites (bionic, focal, jammy, kinetic, lunar, trusty, upstream, xenial): not-affected 3, released 3, ignored 2. https://ubuntu.com/security/CVE-2022-26306

Affected software / configurations for CVE-2022-26306

Vendor Product Version Raw CPE
libreoffice libreoffice >= 7.2.0, < 7.2.7 cpe:2.3:a:libreoffice:libreoffice:*:*:*:*:*:*:*:*
libreoffice libreoffice >= 7.3.0, < 7.3.3 cpe:2.3:a:libreoffice:libreoffice:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-26306

cvelogic Threat Intelligence