Skip to main content
VulnerabilityPublished Updated

CVE-2026-90455: CISA Malcolm · Dependency on Vulnerable Third-party Component

Affects CISA MalcolmSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to v26.06.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in v26.06.0, 26.06.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Malcolm to v26.06.0; Malcolm to 26.06.0.

Affected software

ProductAffectedFixed in
CISAMalcolmAffected
  • <26.06.0
Fixed in
  • v26.06.0
GitHubMalcolmpkg:github/MalcolmOther threatsAffected
  • <26.06.0
Fixed in
  • 26.06.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the limited exploitability, immediate urgent action may not be required, but updating the HTTP client library to a non-vulnerable version is recommended once available.

Description

A prior update that raised a bundled HTTP client library to a version remediating known vulnerabilities was later reverted, reintroducing the earlier, vulnerable version into a log-processing component. The only code path in that component using the library issues a request to a single fixed, trusted vendor URL at initialization and does not process attacker-controlled input through the library, limiting practical exploitability of the reintroduced version in this context.

References

Community reviews

Loading reviews…