---
id: CVE-2026-49462
title: >-
  NL Portal Backend Libraries provide backend components for Dutch government
  portals that interact with residents, customers, suppliers, and partner
  organizations
summary: >-
  NL Portal Backend Libraries provide backend components for Dutch government
  portals that interact with residents, customers, suppliers, and partner
  organizations. In versions up to and including 3.0.0, deployments using the
  shipped defau…
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'
cwe:
  - CWE-200
  - CWE-1188
vendor: nl-portal
product: 'nl.nl-portal:app'
affected:
  - 'nl.nl-portal:app < 3.0.1'
published: '2026-09-11'
updated: '2026-09-14'
sourceUpdated: '2026-09-14T17:17:44.820'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-49462'
references:
  - url: >-
      https://github.com/nl-portal/nl-portal-backend-libraries/commit/0d2af7665a737e91565352bd4e6124cacaa853b7
    label: security-advisories@github.com
  - url: >-
      https://github.com/nl-portal/nl-portal-backend-libraries/security/advisories/GHSA-9m9w-2vqr-m384
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-09-14T16:19:32.111645Z'
epss: 0.00396
epssPercentile: 0.30993
ingestedAt: '2026-09-14T12:48:02.568Z'
---

## Overview

NL Portal Backend Libraries provide backend components for Dutch government portals that interact with residents, customers, suppliers, and partner organizations. In versions up to and including 3.0.0, deployments using the shipped default configuration exposed two GraphQL developer features without requiring authentication: the GraphiQL playground, an interactive UI for issuing GraphQL queries; and schema introspection, which lets a caller download the full description of every query, mutation, type, and argument the API supports. Anyone who could reach the `/graphiql` endpoint could open the playground in a browser, pull the full schema, and use that to map out the API and craft calls against it. By itself this does not leak user data, but it removes the guesswork from attacking the rest of the API and significantly lowers the bar for finding and exploiting other weaknesses. Version 3.0.1 patches the issue. As a workaround, override the two settings in deployed configuration.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.