Skip to main content
Mallory
HighVulnerability

CVE-2019-11248: Information Disclosure via Exposed /debug/pprof Endpoint in Kubernetes Kubelet

Published Aug 29, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v3.1
EPSS75.1%100th percentile
CISA KEVNoNot listed
In the wildReported304 exploitation records in Mallory
Vendor
Kubernetes
IdentifiersCVE-2019-11248CWE-200

CVE-2019-11248 describes an information disclosure vulnerability in Kubernetes Kubelet, where the /debug/pprof debugging endpoint is exposed over the unauthenticated healthz port. This endpoint, intended for profiling and debugging, can leak sensitive information such as internal memory addresses and configuration details. The vulnerability affects Kubernetes versions prior to 1.15.0, 1.14.4, 1.13.8, and 1.12.10. The issue is not exposed by default configuration but can be present in misconfigured environments.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker with network access to the Kubelet healthz port can access the /debug/pprof endpoint without authentication. This can lead to information disclosure, including internal memory addresses and configuration data, which may facilitate further attacks. Additionally, the endpoint can be abused for limited denial-of-service attacks, potentially causing instability or outages in affected Kubernetes nodes or pods.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the Kubelet healthz port using firewall rules or network policies. Disable or secure the /debug/pprof endpoint if not required. Enforce authentication and authorization for all debugging and profiling endpoints. Regularly audit Kubernetes configurations to ensure that sensitive endpoints are not exposed to unauthorized users.

Remediation

Patch, then assume compromise.

Upgrade Kubernetes to version 1.15.0, 1.14.4, 1.13.8, or 1.12.10 or later, where the exposure of the /debug/pprof endpoint over the unauthenticated healthz port is addressed. Ensure that the Kubelet healthz port is not exposed to untrusted networks and that access to debugging endpoints is properly restricted.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
KubernetesKubernetesapplication
FAQ

Frequently asked questions

Is CVE-2019-11248 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-11248?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-11248.
Is there a patch for CVE-2019-11248?
Upgrade Kubernetes to version 1.15.0, 1.14.4, 1.13.8, or 1.12.10 or later, where the exposure of the /debug/pprof endpoint over the unauthenticated healthz port is addressed. Ensure that the Kubelet healthz port is not exposed to untrusted networks and that access to debugging endpoints is properly restricted.
What products are affected by CVE-2019-11248?
Kubernetes.
How severe is CVE-2019-11248?
CVE-2019-11248 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 75.1% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.