Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-14047: A local vulnerability in the Winlogbeat Windows installer caused runtime files to be placed in a directory wri

26
Routine
HIGH 7.2UPGRADE

CVE-2024-14047 is a high-severity flaw (CVSS 7.2) affecting winlogbeat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A local vulnerability in the Winlogbeat Windows installer caused runtime files to be placed in a directory writable by unprivileged users. A low-privileged attacker with existing access to the system could pre-position malicious filesystem links, causing a subsequent elevated Winlogbeat operation to write to or delete arbitrary files. Successful exploitation could result in a denial of service.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorLocal
Attack complexityHigh
Privileges neededLow
User interactionRequired
EPSS exploit chance0.1% (top 96%)
CISA exploited listNo
WeaknessCWE-59
Published2026-09-01
Last modified2026-09-10
Publisher (CNA): Elastic · Vendor: elastic

Share: LinkedIn · X · Reddit

Last updated 2026-09-10 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

elastic winlogbeat UPGRADE
Affected: >= 7.6.0 and < 8.13.0
Fixed in: 8.13.0
Safe to downgrade to: a release before 7.6.0
1. Check installed version
apt-cache policy winlogbeat || rpm -q winlogbeat || winlogbeat --version
2. UPGRADE to 8.13.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade winlogbeat
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade winlogbeat
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 7.6.0 (Debian / Ubuntu)
apt-cache madison winlogbeat sudo apt install winlogbeat=<VERSION_BEFORE_7.6.0> sudo apt-mark hold winlogbeat
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list winlogbeat sudo dnf downgrade winlogbeat-<VERSION_BEFORE_7.6.0> sudo dnf versionlock add winlogbeat
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-14047?

winlogbeat: upgrade to 8.13.0. Exact commands for each OS are on this page.

Is CVE-2024-14047 being exploited?

CVE-2024-14047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-14047 affect?

CVE-2024-14047 affects winlogbeat. Severity is high (CVSS 7.2). A local vulnerability in the Winlogbeat Windows installer caused runtime files to be placed in a directory writable by unprivileged users. A low-privileged attacker with existing access to the system could pre-position malicious filesystem

How urgent is CVE-2024-14047?

Priority 26/100. High severity

Software pages

Windows vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.