CVE-2026-54548

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
3.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

kas is a setup tool for bitbake based projects. Prior to 5.4, internal SSH key setup triggered by SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE creates ~/.ssh/config when no user-specific SSH configuration exists and adds a global Host * rule containing StrictHostKeyChecking no. In kas/libcmds.py, ssh_no_host_key_check() runs without checking ctx.managed_env, so the setting persists after kas exits and affects future SSH sessions by the same local user, extending beyond the intended short-lived continuous integration environment. A later SSH connection can therefore accept an attacker-controlled host key without verification, increasing the risk of a man-in-the-middle attack that compromises session confidentiality or integrity. This issue is fixed in version 5.4.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 9, 2026

References (3)

Vendor Advisories for CVE-2026-54548(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
kas3.1-2 ... 5.5-1 (20 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
kas4.8.1-2 ... 5.5-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
kas4.8.1-2 ... 5.3-1 (6 versions)
  • every version up to 5.4-1: fixed in 5.4-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
kas0.11.0 ... 5.3 (52 versions)
  • every version up to 5.4: fixed in 5.4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-12 15:56 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-08 02:14 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-04 23:10 UTCEG score recompute
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-01 19:57 UTCEG score recompute
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-28 15:50 UTCEG score recompute
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 29 more
  1. 2026-09-25 12:35 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-09-23 17:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-09-19 06:23 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-09-17 19:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-09-16 03:20 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-09-13 00:16 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-09-09 21:13 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-09-08 04:33 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-05 01:30 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-09-01 22:27 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-08-30 01:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-08-29 19:24 UTCEG score recompute
  25. 2026-08-27 14:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-08-26 16:21 UTCEG score recompute
  27. 2026-08-26 15:50 UTCEG score recompute
  28. 2026-08-26 14:23 UTCEG score recomputeFirst assessed: 3.3 LOW
  29. 2026-08-26 14:22 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:12:kas · Debian:13:kas

Frequently asked(5)

What is CVE-2026-54548?
CVE-2026-54548 is a low-severity vulnerability; its CVE record was published on August 26, 2026. kas is a setup tool for bitbake based projects. Prior to 5.4, internal SSH key setup triggered by SSHPRIVATEKEY or SSHPRIVATEKEYFILE creates ~/.ssh/config when no user-specific SSH configuration exists and adds a global Host * rule containing StrictHostKeyChecking no. In kas/libcmds.py,…
When was the CVE record for CVE-2026-54548 published?
The CVE record for CVE-2026-54548 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-54548 actively exploited?
CVE-2026-54548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54548?
CVE-2026-54548 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54548?
A fix for CVE-2026-54548 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54548 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54548

Explore →

Is Your Infrastructure Affected by CVE-2026-54548?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs