Path traversal in Reposilite javadoc file expansion (arbitrary file creation/overwrite) (GHSL-2024-073)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-36116: 1.47% estimated exploitation activity in the next 30 days; percentile 73.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Reposilite v3.5.10 is affected by an Arbitrary File Upload vulnerability via path traversal in expanding of Javadoc archives. Details Reposilite provides support for JavaDocs files, which are archives that contain documentation for artifacts. Specifically, JavadocEndpoints.kt controller allows to expand the javadoc archive into the server's file system and return its content. The problem is in the way how the archives are expanded, specifically how the new filename is created: JavadocContainerService.kt#L127-L136 The file.name taken from the archive can contain path traversal characters, such as '/../../../anything.txt', so the resulting extraction path can be outside the target directory. Impact If the archive is taken from an untrusted source, such as Maven Central or JitPack for example, an attacker can craft a special archive to overwrite any local file on Reposilite instance. This could lead to remote code execution, for example by placing a new plugin into the…

Published by the source

2 Aug 2024, 21:13 UTC

Last modified by the source

2 Aug 2024, 21:32 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-frvj-cfq4-3228

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-36116

Advisory: Path traversal in Reposilite javadoc file expansion (arbitrary file creation/overwrite) (`GHSL-2024-073`)
IDs: CVE-2024-36116, GHSA-frvj-cfq4-3228
Record: https://patchnext.com/advisories/cve-2024-36116 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.reposilite:reposilite-backend 3.5.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.reposilite:reposilite-backend: affected >= 3.3.0, < 3.5.12; fixed in 3.5.12

## Suggested inspection (read-only)
- Maven com.reposilite:reposilite-backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.reposilite:reposilite-backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-frvj-cfq4-3228 (GitHub-reviewed advisory GHSA-frvj-cfq4-3228 lists affected ranges: Maven com.reposilite:reposilite-backend >=3.3.0 <3.5.12)

Commands are suggestions: review each one before running it.