Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container.

published 2019-03-17 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-3766

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress.

Patch / fix

fixed in 1

puppet discovery 1.4.0

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

Puppet Puppet Discovery

Classification

Weakness

CWE-295 Improper Certificate Validation

References

puppet.com /security/cve/CVE-2018-11747
vendor-advisory
lists.apache.org /thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E
mailing-list

Sources

CVE List CVE-2018-11747
NVD CVE-2018-11747

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary