# Temporary Directory Hijacking to Local Privilege Escalation Vulnerability in org.springframework.boot:spring-boot Advisory record · `GHSA-cm59-pr5q-cw85` - **Identifiers:** `GHSA-cm59-pr5q-cw85` · `CVE-2022-27772` - **State:** Confirmed - **Severity:** CVSS 7.8 High - **Critical:** No - **Weakness (CWE):** [CWE-377](https://cwe.mitre.org/data/definitions/377.html) · [CWE-379](https://cwe.mitre.org/data/definitions/379.html) · [CWE-668](https://cwe.mitre.org/data/definitions/668.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-377](https://agentprime.io/advisories/tag/cwe-377.md) · [CWE-379](https://agentprime.io/advisories/tag/cwe-379.md) - **Published:** 11 Jul 2022 - **Updated:** 8 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 11 Jul 2022, 20:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.springframework.boot:spring-boot` (Maven): affected `<2.2.11.RELEASE`; fixed in `2.2.11.RELEASE` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Spring Boot (org.springframework.boot:spring-boot) versions before 2.2.11.RELEASE are vulnerable to temporary directory hijacking in the createTempDir method, which creates the work directory for embedded web servers such as Tomcat and Jetty. A local attacker on an affected system who can write to that shared temporary directory could take over the application and escalate privileges. Upgrade to version 2.2.11.RELEASE or later. As a workaround, set the java.io.tmpdir property to a directory owned exclusively by the user running the application. Written 2 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.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0060, the 48th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cm59-pr5q-cw85) ## Sources - [GitHub Advisory Database: GHSA-cm59-pr5q-cw85](https://github.com/advisories/GHSA-cm59-pr5q-cw85) - [OSV: GHSA-cm59-pr5q-cw85](https://osv.dev/vulnerability/GHSA-cm59-pr5q-cw85) - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .