TCC privilege bypass via directly executed Python launcher
Published Dec 15, 2025 · Updated Dec 15, 2025
Authentication bypass in LibreOffice 25.2 through 25.2.3 on macOS allows local users to run scripts with the application’s TCC privileges. The bundled Python launcher is directly executable and inherits TCC grants assigned to the main application bundle without enforcing its parent process. Exploitation requires local low-privileged execution and prior user-granted TCC access for LibreOffice, exposing only data or services covered by those grants.
Summary
What happened
Authentication bypass in LibreOffice 25.2 through 25.2.3 on macOS allows local users to run scripts with the application’s TCC privileges. The bundled Python launcher is directly executable and inherits TCC grants assigned to the main application bundle without enforcing its parent process. Exploitation requires local low-privileged execution and prior user-granted TCC access for LibreOffice, exposing only data or services covered by those grants.
The record
- CVE
- CVE-2025-14714
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CWE-288, CAPEC-115, T1548.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=25.2 << 25.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo