Advisory record · GHSA-6wxm-mpqj-6jpf

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

CVSS 7.1 HighEPSS 0.0032 · 24th percentile

Published by the GitHub Advisory Database at 28 Jan 2025, 17:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/golang/glogGo<1.2.41.2.4
Identifiers
GHSA-6wxm-mpqj-6jpf · CVE-2024-45339 · GO-2025-3372
Weakness (CWE)
CWE-61 · CWE-377
Published
28 Jan 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of github.com/golang/glog before 1.2.4 are vulnerable. A local attacker who can write to a world-writable log directory, which is the default, can predict a privileged process's log file path and place a symbolic link there that points to a sensitive file, and the privileged process then overwrites that file. Upgrade to glog 1.2.4, which makes the program exit with status code 2 when the log file already exists.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0032, the 24th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.