CVE-2026-23989GO-2026-4444GHSA-9J2F-3RJ3-WGPG
REVA Public Link Exploit
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.40.3, 2.42.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
REVA is an interoperability platform. Prior to 2.42.3 and 2.40.3, a bug in the GRPC authorization middleware of the "Reva" component of OpenCloud allows a malicious user to bypass the scope verification of a public link. By exploiting this via the the "archiver" service this can be leveraged to create an archive (zip or tar-file) containing all resources that this creator of the public link has access to. This vulnerability is fixed in 2.42.3 and 2.40.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- opencloud-eu reva
fixed in 2.40.3; From 2.41.0 · fixed in 2.42.3
- github.com/opencloud-eu/revaGo
All versions
- github.com/opencloud-eu/reva/v2Go
fixed in 2.40.3; From 2.41.0 · fixed in 2.42.3
- github.com/opencloud-eu/reva/v2Go
fixed in 2.40.3
- github.com/opencloud-eu/reva/v2Go
From 2.41.0 · fixed in 2.42.3