Reposilite reflected XSS in directory listing pages
- Exploited
- No known exploitation
- Fix
- Fixed in 3.6.0
- Who is exposed
- Not reported
Summary
Reposilite, a repository manager for Maven artifacts, has a reflected cross-site scripting flaw in its directory listing pages. A network attacker who already has high-level privileges and can get a user to open a crafted link could run scripts in the Admin UI and potentially steal a manager token, which could lead to full instance compromise.
Written by a model
Original description
Reposilite is lightweight and easy-to-use repository management software dedicated to Maven-based artifacts in the JVM ecosystem. From 3.5.16 until 3.6.0, as stated by the advisory, the Maven directory-index page interpolates the request URI without HTML escaping in its title, heading, base URL, and parent-directory link. The advisory says the content-embedded ctx.uri() is percent-encoded, preventing tag injection, but that a single quote passes through and breaks the quoted Parent-Directory link; it also says Location.of strips single quotes, so the reachability of the described quote-based trigger remains unresolved. The listing shares the Admin UI origin and does not set the sandbox Content-Security-Policy used for artifact and Javadoc responses, so the reported script execution could access a user's local-storage token. A manager token could enable full instance compromise. The advisory reports version 3.6.0 as fixed.
What to do
Upgrade to a fixed version: 3.6.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-53526 (Reposilite: Reflected XSS in directory listing pages (privilege escalation via token theft)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-53526 (entry last updated 2026-11-19):
Affected:
- dzikoysk reposilite: from 3.5.16, fixed in 3.6.0
Fixed versions: 3.6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-53526 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-53526 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/dzikoysk/reposilite/security/advisories/GHSA-7944-89x5-52q9
- https://github.com/dzikoysk/reposilite/releases/tag/3.6.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-53526
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-53526"}.Affected versions
- dzikoysk reposiliteFrom 3.5.16 · fixed in 3.6.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.7/10CVSS 5.7
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · dzikoysk/reposilite · Advisory GHSA-7944-89x5-52q9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-53526 |
| Record | NVD · CVE-2026-53526 |
| Other links 1 | |
| Repository | GitHub · dzikoysk/reposilite · Release 3.6.0 |
Questions about CVE-2026-53526
Is CVE-2026-53526 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-53526?
reposilite: from 3.5.16 before 3.6.0.
Source: cve.now feed data
How do I fix CVE-2026-53526?
Upgrade to a fixed version: 3.6.0.
Source: cve.now feed data
Related
- CVE-2024-36117Path traversal while serving Reposilite javadoc expanded files
- CVE-2024-36116Path traversal in Reposilite javadoc file expansion
- CVE-2024-36115Stored Cross site scripting in Reposilite artifacts
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
No corrections so far. Something wrong on this page? Report an error.