# CVE-2026-4933: Unpublished Node Permissions - Critical - Access bypass - SA-CONTRIB-2026-029

> Attackers can bypass access controls to view unpublished nodes in the Drupal Unpublished Node Permissions module.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** DRUPAL-CONTRIB-2026-029, GHSA-3mvf-x53v-pjr7

## What is CVE-2026-4933?

CVE-2026-4933 is a high-severity missing authorization vulnerability in Drupal Unpublished Node Permissions, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Authorization vulnerability in Drupal Unpublished Node Permissions allows Forceful Browsing.This issue affects Unpublished Node Permissions: from 0.0.0 before 1.7.0.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-4933?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/unpublished_node_permissions` | Packagist:https://packages.drupal.org/8 | All versions | 1.7.0 |

Products: Jeroenb Unpublished Node Permissions.

## How do I fix CVE-2026-4933?

Upgrade to a fixed version.

## Is CVE-2026-4933 being exploited?

There is no known exploitation of CVE-2026-4933 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4933 and fix it if it is affected.

What it is: CVE-2026-4933 is a high-severity missing authorization vulnerability in Drupal Unpublished Node Permissions, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4933 in the wild and no public exploit code.

Affected product: Drupal Unpublished Node Permissions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4933/ (Markdown: https://insights.sbomify.com/CVE-2026-4933/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4933
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4933
- OSV: https://osv.dev/vulnerability/CVE-2026-4933

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4933/
Summaries are generated and may contain mistakes; the official description above is the record.