# RPLY Predictable Tmpfile Names Allows Cache Spoofing

Advisory record · `GHSA-9gcf-pq99-rjw3`

- **Identifiers:** `GHSA-9gcf-pq99-rjw3` · `CVE-2014-1604` · `PYSEC-2014-117` · `PYSEC-2014-17`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-377](https://cwe.mitre.org/data/definitions/377.html)
- **Tags:** [CWE-377](https://agentprime.io/advisories/tag/cwe-377.md)
- **Published:** 17 May 2022
- **Updated:** 9 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 01:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `rply` (PyPI): affected `<0.7.1`; fixed in `0.7.1`

## Machine-written summary

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

> RPLY (python-rply) versions before 0.7.1 are affected. A local user can exploit predictable temporary file names in the parser cache to plant a fake cache file, which can spoof the cached parser data. Upgrade rply to version 0.7.1 or later. No workaround is listed.

Written 6 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9gcf-pq99-rjw3)

## Sources

- [GitHub Advisory Database: GHSA-9gcf-pq99-rjw3](https://github.com/advisories/GHSA-9gcf-pq99-rjw3)
- [OSV: GHSA-9gcf-pq99-rjw3](https://osv.dev/vulnerability/GHSA-9gcf-pq99-rjw3)
- <https://nvd.nist.gov/vuln/detail/CVE-2014-1604>
- <https://github.com/alex/rply/commit/fc9bbcd25b0b4f09bbd6339f710ad24c129d5d7c>
- <https://exchange.xforce.ibmcloud.com/vulnerabilities/90593>
- <https://github.com/alex/rply>
- <https://github.com/pypa/advisory-database/tree/main/vulns/rply/PYSEC-2014-117.yaml>
- <https://github.com/pypa/advisory-database/tree/main/vulns/rply/PYSEC-2014-17.yaml>
- <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735263>
- <http://www.openwall.com/lists/oss-security/2014/01/17/8>
- <http://www.openwall.com/lists/oss-security/2014/01/18/4>

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-9gcf-pq99-rjw3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9gcf-pq99-rjw3/>. Everything for agents: <https://agentprime.io/llms.txt>.