OpenCloud Affected by Public Link Exploit

Exploitation

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

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact A security issue was discovered in Reva that enables a malicious user to bypass the scope validation of a public link. That allows it to access resources outside the scope of a public link. OpenCloud uses Reva as one of its core components and thus it is affected. Patches Update to OpenCloud version = 4.0.3 (stable release) Update to OpenCloud version = 5.0.2 (rolling release) Workarounds If projects are unable to update immediately, please implement the following security configuration to disable public link shares temporarily until the final solution for this problem is rolled out. Configuration Adjustment Docker Compose: Edit the docker-compose.yml and add GATEWAYSTORAGEPUBLICLINKENDPOINT=“” (empty string value) in the environment section of the opencloud container. Verification of Mitigation Execute the following test: - Create a public link for testing. - Open the link url in a private (no active login) browser tab. - An error page with “unknown error” will be displayed.…

Published by the source

5 Feb 2026, 21:29 UTC

Last modified by the source

5 Feb 2026, 21:29 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vf5j-r2hw-2hrw

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

# Patch Next advisory brief: GHSA-vf5j-r2hw-2hrw

Advisory: OpenCloud Affected by Public Link Exploit
IDs: GHSA-vf5j-r2hw-2hrw
Record: https://patchnext.com/advisories/ghsa-vf5j-r2hw-2hrw (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/opencloud-eu/opencloud 5.0.2, 4.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/opencloud-eu/opencloud: affected >= 4.0.0, < 4.0.3; >= 5.0.0, < 5.0.2; fixed in 4.0.3, 5.0.2

## Suggested inspection (read-only)
- Go github.com/opencloud-eu/opencloud: 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 github.com/opencloud-eu/opencloud.
- 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-vf5j-r2hw-2hrw (GitHub-reviewed advisory GHSA-vf5j-r2hw-2hrw lists affected ranges: Go github.com/opencloud-eu/opencloud >=4.0.0 =5.0.0 <5.0.2)

Commands are suggestions: review each one before running it.