# Apache Sling Authentication Service vulnerability

Advisory record · `GHSA-vcvp-89fq-hwj8`

- **Identifiers:** `GHSA-vcvp-89fq-hwj8` · `CVE-2017-15700`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 14 May 2022
- **Updated:** 9 Aug 2024
- **Reviewed by a person:** No

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

## Affected packages

- `org.apache.sling:org.apache.sling.auth.core` (Maven): affected `>=1.4.0, <1.4.2`; fixed in `1.4.2`

## Machine-written summary

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

> Apache Sling Authentication Service (org.apache.sling:org.apache.sling.auth.core) versions 1.4.0 through 1.4.1 are affected. An attacker can use the Sling login form to trick a victim into sending their credentials. Upgrade to version 1.4.2 or later.

Written 8 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.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vcvp-89fq-hwj8)

## Sources

- [GitHub Advisory Database: GHSA-vcvp-89fq-hwj8](https://github.com/advisories/GHSA-vcvp-89fq-hwj8)
- [OSV: GHSA-vcvp-89fq-hwj8](https://osv.dev/vulnerability/GHSA-vcvp-89fq-hwj8)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-15700>
- <https://github.com/apache/sling-org-apache-sling-auth-core>
- <https://lists.apache.org/thread.html/182bed1dd6933824a81cc5f07639eeb813fbd8f2cc49d51b452ab621@%3Cdev.sling.apache.org%3E>

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-vcvp-89fq-hwj8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vcvp-89fq-hwj8/>. Everything for agents: <https://agentprime.io/llms.txt>.
