NL Portal: Missing per-user authorization on document and decision GraphQL queries in nl-portal-backend-libraries
CVE-2026-49463GHSA-qpm9-h556-mwxm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (nl.nl-portal:besluiten 3.0.1; nl.nl-portal:documenten-api 3.0.1), 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.
Affected packages
Maven nl.nl-portal:besluiten
- Affected
- >= 1.5.0, <= 3.0.0
- Fixed in
- 3.0.1
Maven nl.nl-portal:documenten-api
- Affected
- <= 3.0.0
- Fixed in
- 3.0.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-qpm9-h556-mwxm lists affected ranges: Maven nl.nl-portal:documenten-api >=0 =1.5.0 <=3.0.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-49463: 0.34% estimated exploitation activity in the next 30 days; percentile 27.58 (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 In versions up to and including 3.0.0, two parts of the GraphQL API returned data without checking whether the data belonged to the logged-in user: - Document content. A logged-in user could download the raw content of any document by its ID, regardless of who owned it. The resolver has lacked an authentication parameter since the initial commit of the project (2022-11-22) — so every version of nl.nl-portal:documenten-api ever published is affected (the earliest one on Maven Central is 0.2.2.RELEASE, published 2023-08-31). - Decisions (besluiten). A logged-in user could list, search, and read decision records — including their audit trails and the documents attached to them — for any user. The list query also accepted filters (decision type, identification, responsible organisation, related case), which made it easy to enumerate decisions across the user base. The besluiten module was introduced in the 1.5.x release line (commit 9229460b, 2024-08-19), so versions of…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-qpm9-h556-mwxm
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-49463 Advisory: NL Portal: Missing per-user authorization on document and decision GraphQL queries in nl-portal-backend-libraries IDs: CVE-2026-49463, GHSA-qpm9-h556-mwxm Record: https://patchnext.com/advisories/cve-2026-49463 (revision 1, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: nl.nl-portal:besluiten 3.0.1; nl.nl-portal:documenten-api 3.0.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven nl.nl-portal:besluiten: affected >= 1.5.0, <= 3.0.0; fixed in 3.0.1 - Maven nl.nl-portal:documenten-api: affected <= 3.0.0; fixed in 3.0.1 ## Suggested inspection (read-only) - Maven nl.nl-portal:besluiten: check the installed version with your package manager. - Maven nl.nl-portal:documenten-api: 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 nl.nl-portal:besluiten, nl.nl-portal:documenten-api. - 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-qpm9-h556-mwxm (GitHub-reviewed advisory GHSA-qpm9-h556-mwxm lists affected ranges: Maven nl.nl-portal:documenten-api >=0 =1.5.0 <=3.0.0) Commands are suggestions: review each one before running it.
Loading voting…