# jooby-pac4j: deserialization of untrusted data

Advisory record · `GHSA-7c5v-895v-w4q5`

- **Identifiers:** `GHSA-7c5v-895v-w4q5` · `CVE-2025-31129`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 1 Apr 2025
- **Updated:** 1 Apr 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Apr 2025, 14:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.jooby:jooby-pac4j` (Maven): affected `<2.17.0 || >=3.0.0.M1, <3.7.0`; fixed in `2.17.0`, `3.7.0`

## Machine-written summary

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

> Versions of io.jooby:jooby-pac4j before 2.17.0, and from 3.0.0.M1 before 3.7.0, are vulnerable to deserialization of untrusted data through session handling. The source describes an attacker supplying a crafted session value, which can lead to code execution; the exact conditions required are not fully detailed. Upgrade to 2.17.0 or 3.7.0. As a workaround, check which values are stored in the session and avoid putting untrusted data there.

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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0066, the 52nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7c5v-895v-w4q5)

## Sources

- [GitHub Advisory Database: GHSA-7c5v-895v-w4q5](https://github.com/advisories/GHSA-7c5v-895v-w4q5)
- [OSV: GHSA-7c5v-895v-w4q5](https://osv.dev/vulnerability/GHSA-7c5v-895v-w4q5)
- <https://github.com/jooby-project/jooby/security/advisories/GHSA-7c5v-895v-w4q5>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-31129>
- <https://github.com/jooby-project/jooby/commit/3e13562cf36d7407813eae464e0f4b598de15692>
- <https://github.com/jooby-project/jooby>
- <https://github.com/jooby-project/jooby/blob/v2.x/modules/jooby-pac4j/src/main/java/io/jooby/internal/pac4j/SessionStoreImpl.java#L39-L45>
- <https://github.com/jooby-project/jooby/blob/v3.6.1/modules/jooby-pac4j/src/main/java/io/jooby/internal/pac4j/SessionStoreImpl.java#L77-L84>

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-7c5v-895v-w4q5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7c5v-895v-w4q5/>. Everything for agents: <https://agentprime.io/llms.txt>.