# CVE-2022-26305: Execution of Untrusted Macros Due to Improper Certificate Validation

> Attackers can bypass macro trust checks by spoofing certificate details, tricking users into executing malicious code in LibreOffice.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-26305, GHSA-fm9c-xcj2-2j5g, UBUNTU-CVE-2022-26305

## What is CVE-2022-26305?

CVE-2022-26305 is a high-severity vulnerability in Libreoffice Libreoffice, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An Improper Certificate Validation vulnerability in LibreOffice existed where determining if a macro was signed by a trusted author was done by only matching the serial number and issuer string of the used certificate with that of a trusted certificate. This is not sufficient to verify that the macro was actually signed with the certificate. An adversary could therefore create an arbitrary certificate with a serial number and an issuer string identical to a trusted certificate which LibreOffice would present as belonging to the trusted author, potentially leading to the user to execute arbitrary code contained in macros improperly trusted. This issue affects: The Document Foundation LibreOffice 7.2 versions prior to 7.2.7; 7.3 versions prior to 7.3.1.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-26305?

It affects 1 product.


Products: Libreoffice Libreoffice.

## How do I fix CVE-2022-26305?

Upgrade to a fixed version.

## Is CVE-2022-26305 being exploited?

There is no known exploitation of CVE-2022-26305 in the wild and no public exploit code.

## Other vulnerabilities in Libreoffice Libreoffice

- [CVE-2024-5261](https://insights.sbomify.com/CVE-2024-5261/): TLS certificate are not properly verified when utilizing LibreOfficeKit (critical 10.0)
- [CVE-2019-9855](https://insights.sbomify.com/CVE-2019-9855/): Windows 8.3 path equivalence handling flaw allows LibreLogo script execution (critical 9.8)
- [CVE-2018-14939](https://insights.sbomify.com/CVE-2018-14939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8358](https://insights.sbomify.com/CVE-2017-8358/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7882](https://insights.sbomify.com/CVE-2017-7882/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26305 and fix it if it is affected.

What it is: CVE-2022-26305 is a high-severity vulnerability in Libreoffice Libreoffice, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-26305 in the wild and no public exploit code.

Affected product: Libreoffice Libreoffice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-26305/ (Markdown: https://insights.sbomify.com/CVE-2022-26305/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26305
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26305
- OSV: https://osv.dev/vulnerability/CVE-2022-26305

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26305/
Summaries are generated and may contain mistakes; the official description above is the record.