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

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

- **Identifiers:** `GHSA-6wxm-mpqj-6jpf` · `CVE-2024-45339` · `GO-2025-3372`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-61](https://cwe.mitre.org/data/definitions/61.html) · [CWE-377](https://cwe.mitre.org/data/definitions/377.html)
- **Tags:** [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md) · [CWE-377](https://agentprime.io/advisories/tag/cwe-377.md)
- **Published:** 28 Jan 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/golang/glog` (Go): affected `<1.2.4`; fixed in `1.2.4`

## 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

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`, from 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

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6wxm-mpqj-6jpf)

## Sources

- [GitHub Advisory Database: GHSA-6wxm-mpqj-6jpf](https://github.com/advisories/GHSA-6wxm-mpqj-6jpf)
- [OSV: GHSA-6wxm-mpqj-6jpf](https://osv.dev/vulnerability/GHSA-6wxm-mpqj-6jpf)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-45339>
- <https://github.com/golang/glog/pull/74>
- <https://github.com/golang/glog/pull/74/commits/b8741656e406e66d6992bc2c9575e460ecaa0ec2>
- <https://github.com/golang/glog>
- <https://groups.google.com/g/golang-announce/c/H-Q4ouHWyKs>
- <https://lists.debian.org/debian-lts-announce/2025/02/msg00019.html>
- <https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File>
- <https://pkg.go.dev/vuln/GO-2025-3372>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6wxm-mpqj-6jpf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6wxm-mpqj-6jpf/>. Everything for agents: <https://agentprime.io/llms.txt>.