Skip to main content
Menu
CVEs

Greenbone gvmd authorization bypass in TLS certificate creation

CVE-2026-133494Published November 19, 2026, updated

4.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 26.43.0
Who is exposed
Not reported

Summary

Greenbone gvmd before a fixed release does not restrict certificate creation, so even the Observer role, which is documented as read-only, can run the create_tls_certificate command. An attacker who can reach the service over the network and log in with a low-privilege account can create TLS certificates they should not be allowed to create.

Written by a model

Original description

Greenbone gvmd before 26.43.0 does not restrict certificate creation. Even the Observer role, documented to be read-only, can execute create_tls_certificate.

What to do

Upgrade to a fixed version: 26.43.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133494 (Greenbone gvmd before 26.43.0 does not restrict certificate creation.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133494 (entry last updated 2026-11-19):
Affected:
- Greenbone gvmd: fixed in 26.43.0
Fixed versions: 26.43.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133494 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133494 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/greenbone/gvmd/pull/3213
- https://github.com/greenbone/gvmd/releases/tag/v26.43.0
- https://tajapps.com/advisories/TAJ-2026-004/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133494
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133494"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-133494

Is CVE-2026-133494 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133494?

gvmd: before 26.43.0.

Source: cve.now feed data

How do I fix CVE-2026-133494?

Upgrade to a fixed version: 26.43.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.