dbcve.org
LibreofficeApplication

CVE-2025-2866

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-27
Fix available
A fix is available. Upgrade to 24.8.6.0 / 25.2.2 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Verification of Cryptographic Signature vulnerability in LibreOffice allows PDF Signature Spoofing by Improper Validation. In the affected versions of LibreOffice a flaw in the verification code for adbe.pkcs7.sha1 signatures could cause invalid signatures to be accepted as valid This issue affects LibreOffice: from 24.8 before < 24.8.6, from 25.2 before < 25.2.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LibreOffice fails to properly verify adbe.pkcs7.sha1 PDF signatures, allowing invalid signatures to be accepted as valid. This enables an attacker to modify a PDF document while maintaining the appearance of a legitimate digital signature, facilitating document spoofing and potential fraud.

MitigationUpgrade LibreOffice to version 24.8.6 or 25.2.2 or later which contain the corrected signature verification code. Users should verify their current LibreOffice version and apply available patches promptly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibreofficeApplication
Affected:>= 24.8.0.1, < 24.8.6.0>= 25.2.0.1, < 25.2.2= 24.8.0.0= 25.2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed LibreOffice version
    Open LibreOffice, go to Help > About (or LibreOffice Writer > About on Mac), or run command: soffice --version on Linux/macOS, or check installed programs list on Windows
    Affected if Version is 24.8.0.0, 24.8.0.1 through 24.8.5.x, 25.2.0.0, or 25.2.0.1 through 25.2.1.x (these fall within < 24.8.6.0 or < 25.2.2)
  2. Verify PDF signature feature usage
    Open any PDF file in LibreOffice Draw or LibreOffice Writer and check if the document contains a digital signature panel or signature validation option (File > Properties > Digital Signatures or View > Signatures)
    Affected if PDF files with adbe.pkcs7.sha1 type signatures are opened and verified using LibreOffice's built-in PDF reader
  3. Identify signature algorithm in use
    When a PDF is signed, inspect the signature properties to confirm the signature scheme is adbe.pkcs7.sha1 (this appears in signature details or certificate information dialog)
    Affected if The PDF uses adbe.pkcs7.sha1 signature scheme which is the specific format this CVE affects

User is affected if LibreOffice version is 24.8.0.0 through 24.8.5.x or 25.2.0.0 through 25.2.1.x AND they open and verify PDF documents with adbe.pkcs7.sha1 digital signatures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.8.6.0 / 25.2.2 or later
Fixed in 24.8.6.025.2.2
Interim mitigation

Upgrade LibreOffice to version 24.8.6 or 25.2.2 or later which contain the corrected signature verification code. Users should verify their current LibreOffice version and apply available patches promptly.

Recommended fix High confidence

24.8.6.0 or later for 24.8.x branch; 25.2.2 or later for 25.2.x branch

  1. Identify your current LibreOffice version by going to Help > About LibreOffice
  2. Download the fixed version from the official LibreOffice website (www.libreoffice.org) or your distribution's package repository
  3. For 24.8.x branch users: Upgrade to version 24.8.6.0 or later
  4. For 25.2.x branch users: Upgrade to version 25.2.2 or later
  5. On Linux: Use your package manager (e.g., sudo apt update && sudo apt upgrade libreoffice on Debian/Ubuntu, or sudo dnf upgrade libreoffice on Fedora)
  6. On Windows: Run the installer and follow the upgrade prompts
  7. On macOS: Download the dmg and replace the existing installation
  8. After upgrade, verify the version by checking Help > About LibreOffice

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libreoffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2866 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data