CVE-2019-9854 [High] | Path Traversal in Libreoffice

LibreOffice has a feature where documents can specify that pre-installed macros can be executed on various script events such as mouse-over, document-open etc. Access is intended to be restricted to scripts under the share/Scripts/python, user/Scripts/python sub-directories of the LibreOffice install. Protection was added, to address CVE-2019-9852, to avoid a directory traversal attack where scripts in arbitrary locations on the file system could be executed by employing a URL encoding attack to defeat the path verification step. However this protection could be bypassed by taking advantage of a flaw in how LibreOffice assembled the final script URL location directly from components of the passed in path as opposed to solely from the sanitized output of the path verification step. This issue affects: Document Foundation LibreOffice 6.2 versions prior to 6.2.7; 6.3 versions prior to 6.3.1.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.55%	1.94%	+1.39%
2	2026-06-11	0.38%	0.55%	+0.17%
3	2026-06-01	—	0.38%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.55%

1.94%

+1.39%

2026-06-11

0.38%

0.55%

+0.17%

2026-06-01

—

0.38%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
6.8	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.6	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

6.8

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.6

6.4

[email protected]

OS Trackers for CVE-2019-9854

vendor	priority	summary	link
`alpine`	high	CVE-2019-9854: 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-2019-9854
`debian`	not yet assigned	CVE-2019-9854 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-2019-9854
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-9854
`suse`	high	CVE-2019-9854 severity important: SUSE including 984 source package names (libreoffice-6.2.7.1-3.24.4, libreoffice-6.2.7.1-43.56.3, …), 1181 product×package rows across 22 product lines (SUSE Linux Enterprise Desktop 12 SP4, SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 SP2, … (22 product lines)): Fixed 1181.	https://www.suse.com/security/cve/CVE-2019-9854/
`ubuntu`	medium	CVE-2019-9854 medium priority: Ubuntu including 1 source packages (libreoffice), 5 status rows across 5 suites (bionic, disco, trusty, upstream, xenial): released 3, DNE 1, needs-triage 1.	https://ubuntu.com/security/CVE-2019-9854

Affected software / configurations for CVE-2019-9854

Vendor	Product	Version	Raw CPE
libreoffice	libreoffice	>= 6.2.0, < 6.2.7	cpe:2.3:a:libreoffice:libreoffice::::::::
libreoffice	libreoffice	>= 6.3.0, < 6.3.1	cpe:2.3:a:libreoffice:libreoffice::::::::
canonical	ubuntu_linux	16.04	cpe:2.3:o:canonical:ubuntu_linux:16.04::::lts:::
canonical	ubuntu_linux	18.04	cpe:2.3:o:canonical:ubuntu_linux:18.04::::lts:::
canonical	ubuntu_linux	19.04	cpe:2.3:o:canonical:ubuntu_linux:19.04:::::::*
debian	debian_linux	8.0	cpe:2.3:o:debian:debian_linux:8.0:::::::*
debian	debian_linux	9.0	cpe:2.3:o:debian:debian_linux:9.0:::::::*
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
fedoraproject	fedora	29	cpe:2.3:o:fedoraproject:fedora:29:::::::*
opensuse	leap	15.0	cpe:2.3:o:opensuse:leap:15.0:::::::*
opensuse	leap	15.1	cpe:2.3:o:opensuse:leap:15.1:::::::*
redhat	enterprise_linux	7.0	cpe:2.3:o:redhat:enterprise_linux:7.0:::::::*
redhat	enterprise_linux	8.0	cpe:2.3:o:redhat:enterprise_linux:8.0:::::::*

References for CVE-2019-9854

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00067.html	Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00055.html	Third Party Advisory
https://lists.debian.org/debian-lts-announce/2019/10/msg00005.html	Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XQKKOIY2DMZCXJINOLIQXD2NWISDKK3N/
https://seclists.org/bugtraq/2019/Sep/17	Mailing List Third Party Advisory
https://usn.ubuntu.com/4138-1/	Third Party Advisory
https://www.debian.org/security/2019/dsa-4519	Third Party Advisory
https://www.libreoffice.org/about-us/security/advisories/CVE-2019-9854/	Vendor Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1769907	Third Party Advisory

URL

CVE-2019-9854 | Unsafe URL assembly flaw in allowed script location check

Exploit prediction scoring system (EPSS) score for CVE-2019-9854

Common vulnerability scoring system (CVSS) metrics for CVE-2019-9854

Weakness enumeration for CVE-2019-9854

OS Trackers for CVE-2019-9854

Affected software / configurations for CVE-2019-9854

References for CVE-2019-9854