NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2018-21019 — homeassistant

HIGHFix: home-assistant/home-assistant#13836

CVE-2018-21019 is a high-severity (CVSS 7.5) Information Exposure vulnerability in homeassistant. A fix is available for homeassistant — see the affected versions and patch details below.

Home Assistant information disclosure vulnerability

Also known asGHSA-mh78-8f49-vjg3PYSEC-2019-221
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk+0.05%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.62%1.16%1.70%2.24%1.3%1.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍homeassistant

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Home Assistant before 0.67.0 was vulnerable to an information disclosure that allowed an unauthenticated attacker to read the application's error log via components/api.py.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIhomeassistantall versions0.67.0pip install --upgrade 'homeassistant==0.67.0'

Affected Products

1 product · 1 configurations
Application
home-assistanthome-assistant
< 0.67.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for homeassistant, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update homeassistant to 0.67.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-21019 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Home Assistant before 0.67.0 was vulnerable to an information disclosure that allowed an unauthenticated attacker to read the application's error log via components/api.py.
O3 Security · Impact-Aware SCA

Is CVE-2018-21019 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2018-21019: homeassistant — Fixed in 0.67.0