NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Insecure Temporary File usage in github.com/golang/glogGHSA-6wxm-mpqj-6jpf

HIGHFix: golang/glog#74

GHSA-6wxm-mpqj-6jpf is a high-severity (CVSS 7.1) vulnerability in github.com/golang/glog. A fix is available for github.com/golang/glog — see the affected versions and patch details below.

Also known asCVE-2024-45339GO-2025-3372
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6wxm-mpqj-6jpf.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk
0.00%0.27%0.55%0.82%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/golang/glog

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

When logs are written to a widely-writable directory (the default), an unprivileged attacker may predict a privileged process's log file path and pre-create a symbolic link to a sensitive file in its place. When that privileged process runs, it will follow the planted symlink and overwrite that sensitive file. To fix that, glog now causes the program to exit (with status code 2) when it finds that the configured log file already exists.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/golang/glogall versions1.2.4go get github.com/golang/glog@v1.2.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/golang/glog, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/golang/glog to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wxm-mpqj-6jpf is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-6wxm-mpqj-6jpf (CC BY 4.0)
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-0:2.479.3.1740464431-3.el8RHSA-2025:2223
Red Hat OpenShift Container Platform 4.12openshift4/cloud-event-proxy-rhel8:v4.12.0-202507240129.p0.g96af0ec.assembly.stream.el8RHSA-2025:12325
Red Hat OpenShift Container Platform 4.14openshift4/ose-agent-installer-api-server-rhel8:v4.14.0-202508051136.p0.g6df4bf1.assembly.stream.el8RHSA-2025:13289
Red Hat OpenShift Container Platform 4.14openshift4/cloud-event-proxy-rhel8:v4.14.0-202508051136.p0.gd173b63.assembly.stream.el8RHSA-2025:13291
Red Hat OpenShift Container Platform 4.15openshift4/ose-agent-installer-csr-approver-rhel8:v4.15.0-202507282305.p0.gf0b1275.assembly.stream.el8RHSA-2025:12370
Red Hat OpenShift Container Platform 4.15openshift4/ose-cloud-event-proxy-rhel9:v4.15.0-202507291037.p0.g1f58d5e.assembly.stream.el9RHSA-2025:12372
Red Hat OpenShift Container Platform 4.16openshift4/ose-aws-cluster-api-controllers-rhel9:v4.16.0-202507220305.p0.g949f38a.assembly.stream.el9RHSA-2025:11681
Red Hat OpenShift Container Platform 4.16openshift4/ose-agent-installer-api-server-rhel9:v4.16.0-202508042206.p0.g5c16119.assembly.stream.el9RHSA-2025:13336

Frequently Asked Questions

When logs are written to a widely-writable directory (the default), an unprivileged attacker may predict a privileged process's log file path and pre-create a symbolic link to a sensitive file in its place. When that privileged process runs, it will follow the planted symlink and overwrite that sensitive file. To fix that, glog now causes the program to exit (with status code 2) when it finds that the configured log file already exists.
O3 Security · Impact-Aware SCA

Is GHSA-6wxm-mpqj-6jpf in your dependencies?

Find it across Go, including transitive dependencies.

Insecure Temporary File usage in github.com/golang/glog