# Liferay Portal and DXP do not properly restrict access to OpenAPI

Advisory record · `GHSA-j82q-c85j-xw4w`

- **Identifiers:** `GHSA-j82q-c85j-xw4w` · `CVE-2025-62256`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 23 Oct 2025
- **Updated:** 15 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Oct 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay:com.liferay.portal.security.auth.verifier` (Maven): affected `<6.0.26`; fixed in `6.0.26`

## Machine-written summary

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

> Liferay Portal and Liferay DXP do not properly restrict access to the OpenAPI definition in certain circumstances, affecting the com.liferay.portal.security.auth.verifier package below 6.0.26. A remote attacker can use a crafted URL to retrieve the OpenAPI YAML file. Upgrade the package to version 6.0.26.

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

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (Liferay)

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

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j82q-c85j-xw4w)

## Sources

- [GitHub Advisory Database: GHSA-j82q-c85j-xw4w](https://github.com/advisories/GHSA-j82q-c85j-xw4w)
- [OSV: GHSA-j82q-c85j-xw4w](https://osv.dev/vulnerability/GHSA-j82q-c85j-xw4w)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-62256>
- <https://github.com/liferay/liferay-portal/commit/1ec03c02f2e0ecfdf4101c1a7ade5353767e62e3>
- <https://github.com/liferay/liferay-portal/commit/27b51dbae35bd6e4b415fb33ecf14b2144b5038f>
- <https://github.com/liferay/liferay-portal/commit/bc6138ce1be22babbd90dc2190f4dbe91c039334>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.atlassian.net/browse/LPE-17884>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-62256>

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-j82q-c85j-xw4w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j82q-c85j-xw4w/>. Everything for agents: <https://agentprime.io/llms.txt>.