# PicketLink does not properly check role based authorization

Advisory record · `GHSA-9qhq-j4xm-cw48`

- **Identifiers:** `GHSA-9qhq-j4xm-cw48` · `CVE-2015-3158`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 17 May 2022
- **Updated:** 6 Dec 2024
- **Reviewed by a person:** No

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

## Affected packages

- `org.picketlink:picketlink-tomcat-common` (Maven): affected `<2.7.1.Final`; fixed in `2.7.1.Final`

## Machine-written summary

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

> PicketLink-tomcat-common versions before 2.7.1.Final do not properly check role-based authorization in the invokeNextValve function of AbstractIDPValve. A remote authenticated user can gain access to restricted application resources, either through a direct request or through a service provider initiated flow. Upgrade org.picketlink:picketlink-tomcat-common to 2.7.1.Final or later.

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

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

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

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9qhq-j4xm-cw48)

## Sources

- [GitHub Advisory Database: GHSA-9qhq-j4xm-cw48](https://github.com/advisories/GHSA-9qhq-j4xm-cw48)
- [OSV: GHSA-9qhq-j4xm-cw48](https://osv.dev/vulnerability/GHSA-9qhq-j4xm-cw48)
- <https://nvd.nist.gov/vuln/detail/CVE-2015-3158>
- <https://github.com/picketlink/picketlink-bindings/pull/124>
- <https://github.com/picketlink/picketlink-bindings/commit/ae6ff4adfc562880e714a089983054b47610ecec>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1216123>
- <https://github.com/picketlink/picketlink-bindings>
- <https://issues.jboss.org/browse/PLINK-708>
- <http://rhn.redhat.com/errata/RHSA-2015-1669.html>
- <http://rhn.redhat.com/errata/RHSA-2015-1670.html>
- <http://rhn.redhat.com/errata/RHSA-2015-1671.html>
- <http://rhn.redhat.com/errata/RHSA-2015-1672.html>
- <http://rhn.redhat.com/errata/RHSA-2015-1673.html>

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

---

The web page: <https://agentprime.io/advisories/GHSA-9qhq-j4xm-cw48/>. Everything for agents: <https://agentprime.io/llms.txt>.
