dbcve.org
LibreofficeApplication

CVE-2025-14714

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-15
Fix available
A fix is available. Upgrade to 25.2.4.1 or later.
See remediation →
67/100
Remediation priority · Elevated
Zero-click

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
An Authentication Bypass vulnerability existed where the application bundled an interpreter (Python) that inherits the Transparency, Consent, and Control (TCC) permissions granted by the user to the main application bundle By executing the bundled interpreter directly the attacker's scripts run with the application's TCC privileges In fixed versions parent-constraints are used to allow only the main application to launch interpreter with those permissions This issue affects LibreOffice on macOS: from 25.2 before < 25.2.4.

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 bundles a Python interpreter on macOS that inherits the TCC (Transparency, Consent, and Control) permissions granted to the main application. By executing the bundled interpreter directly, attackers can run scripts with the application's TCC privileges (e.g., accessibility, screen recording), bypassing normal authentication controls. Fixed versions implement parent-constraints to ensure only the main application can launch the interpreter with those elevated permissions.

MitigationUpgrade LibreOffice to version 25.2.4 or later on macOS, which implements parent-constraint validation to prevent unauthorized access to the bundled interpreter.

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:>= 25.2.0.1, < 25.2.4.1

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Confirm macOS platform
    Verify the operating system is macOS. This vulnerability only affects macOS builds of LibreOffice. Run 'uname -s' or check System Preferences.
    Affected if Running any operating system other than macOS means this CVE does not apply.
  2. Identify installed LibreOffice version
    Open LibreOffice and go to LibreOffice > About LibreOffice, or run 'defaults read /Applications/LibreOffice.app/Contents/Info.plist CFBundleShortVersionString' in Terminal.
    Affected if Version is 25.2.0.1 or higher but lower than 25.2.4.1, meaning it falls within the range >= 25.2.0.1 and < 25.2.4.1.
  3. Locate bundled Python interpreter
    Check for the presence of a Python binary within the LibreOffice application bundle at路径 such as /Applications/LibreOffice.app/Contents/Frameworks/Python.framework/Versions/Current/bin/python3 or similar paths within the app bundle.
    Affected if The bundled Python interpreter exists within the LibreOffice application bundle.
  4. Test direct execution of bundled interpreter
    Attempt to execute the bundled Python directly from Terminal, for example: '/Applications/LibreOffice.app/Contents/Frameworks/Python.framework/Versions/Current/bin/python3 --version'. If it runs without requiring the main LibreOffice application as parent process, the environment is vulnerable.
    Affected if The bundled Python interpreter executes successfully when launched directly, without validation that the parent process is the main LibreOffice application.

A user is affected if running macOS with LibreOffice version 25.2.0.1 through 25.2.3.x installed, where the bundled Python interpreter can be executed directly and inherits the application's TCC permissions.

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 25.2.4.1 or later
Fixed in 25.2.4.1
Interim mitigation

Upgrade LibreOffice to version 25.2.4 or later on macOS, which implements parent-constraint validation to prevent unauthorized access to the bundled interpreter.

Recommended fix High confidence

LibreOffice 25.2.4 or later

  1. Navigate to www.libreoffice.org and download LibreOffice version 25.2.4 or later for macOS
  2. Uninstall the current vulnerable LibreOffice version (25.2.0.1 through 25.2.3.x)
  3. Install the fixed LibreOffice 25.2.4 or later version
  4. Verify the fix by launching LibreOffice and checking Help > About LibreOffice confirms version 25.2.4 or higher

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

Fix this in Libreoffice Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14714 — 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-14714 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