Skip to main content
CVE-2026-97045VulnerabilityPublished

Kedacore http add on:

Affects kedacore-http-add-onSource GCVE Database

0
Compare
Authoritative record:CVE-2026-97045· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 0.16.0-r0 when convenient.

Data as of 6 Nov 2026, 04:21 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.16.1
Patch
Available – fixed in 0.16.0-r0, 0.18.1-r13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 5 Nov 2026.

What to do

Upgrade kedacore-http-add-on to 0.16.0-r0; restic to 0.18.1-r13.

Affected software

ProductAffectedFixed in
CleanStartkedacore-http-add-onpkg:apk/cleanstart/kedacore-http-add-onOther threatsAffected
  • <0.16.0-r0
Fixed in
  • 0.16.0-r0
CleanStartresticpkg:apk/cleanstart/resticOther threatsAffected
  • <0.18.1-r13
Fixed in
  • 0.18.1-r13

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

AI-suggested

Apply the official patches by upgrading to kedacore-http-add-on versions 0.16.0-r0 or 0.18.1-r13 or later. Since a patch is available, remediation through upgrading is the recommended action. No additional mitigation steps are indicated.

Description

CVE-2026-97045 is a medium severity vulnerability in the kedacore-http-add-on affecting versions prior to 0.16.0-r0 and 0.18.1-r13. The issue involves the function childTextNodesAreLiteral, where the logic for walking up the DOM tree incorrectly stopped at the nearest foreign ancestor upon encountering an HTML integration point. This could lead to partial bypass or incorrect processing of HTML content. A fix is available in versions 0.16.0-r0 and 0.18.1-r13.

References

Community reviews

Loading reviews…