Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Sulu: Fix authorization bypass when creating preview links

CVE-2026-82394GHSA-65cv-w493-7vhq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sulu/sulu 3.0.8, 2.6.25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist sulu/sulu

    Affected
    <= 2.6.24>= 3.0.0-alpha1, < 3.0.8
    Fixed in
    3.0.8, 2.6.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-82394: 0.58% estimated exploitation activity in the next 30 days; percentile 47.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A missing authorization check on the preview link endpoint lets a backend user create a public, unauthenticated preview URL for content they are not allowed to see. PreviewLinkController (and the underlying PreviewLinkManager::generate() / revoke()) never enforced a permission on the target resource. Any authenticated administration user could call the generate action for any page, article or snippet, including content in a webspace or area they have no VIEW rights on. The endpoint returns a public render URL that resolves the content solely by an opaque token, so the attacker (or anyone they share the link with) can then read the restricted content without authentication. This affects installations that use Sulu role and webspace permissions to restrict who may see certain content. Exploitation requires an authenticated backend user and the id of the target resource. Patches Fixed in 2.6.x and 3.0.x. PreviewLinkManager::generate() and revoke() now resolve the resource's…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-65cv-w493-7vhq

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-65cv-w493-7vhq

Agent brief

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

# Patch Next advisory brief: CVE-2026-82394

Advisory: Sulu: Fix authorization bypass when creating preview links
IDs: CVE-2026-82394, GHSA-65cv-w493-7vhq
Record: https://patchnext.com/advisories/cve-2026-82394 (revision 3, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sulu/sulu 3.0.8, 2.6.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sulu/sulu: affected <= 2.6.24; >= 3.0.0-alpha1, < 3.0.8; fixed in 3.0.8, 2.6.25

## Suggested inspection (read-only)
- Packagist sulu/sulu: 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 sulu/sulu.
- 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://osv.dev/vulnerability/GHSA-65cv-w493-7vhq (OSV record GHSA-65cv-w493-7vhq lists affected ranges: Packagist sulu/sulu >=0 =3.0.0-alpha1 <3.0.8 (fixed))
- Verified: https://github.com/advisories/GHSA-65cv-w493-7vhq (GitHub-reviewed advisory GHSA-65cv-w493-7vhq lists affected ranges: Packagist sulu/sulu >=0 =3.0.0-alpha1 <3.0.8)

Commands are suggestions: review each one before running it.

Loading voting…