CVE Intelligence
Medium Injection

CVE-2026-19266 — Kirachon context-engine review-git-diff Endpoint gitUtils.ts execGitCommand command injection

A vulnerability was determined in Kirachon context-engine up to 1.9.0. This affects the function execGitCommand of the file src/mcp/utils/gitUtils.ts of the component review-git-diff Endpoint. Executing a manipulation of the argument args can lead to command injection. Upgrading to version 1.9.1 mitigates this issue. This patch is called e0729dcfd3a2b1682a7bff86e7174852c03419ba. It is advisable to upgrade the affected component.

Published Aug 8, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Kirachon
Context-engine
CVSS base
5.5
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Kirachon Context-engine).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Kirachon Context-engine version 1.0version 1.1version 1.2version 1.3version 1.4version 1.5version 1.6version 1.7
and 2 more version 1.8version 1.9.0
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.1 CVSS 4.0 Medium — — cna@vuldb.com via NIST National Vulnerability Database
5.1 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.5 CVSS 3.1 Medium 2.1 3.4 cna@vuldb.com via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.5 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.2 CVSS 2.0 Medium 5.1 6.4 cna@vuldb.com via NIST National Vulnerability Database
5.2 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-74 · Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
application logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · kirachon/context-engine
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 5.5
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Aug 8, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

9 on the record

Elsewhere on this site

Kirachon
every CVE for this vendor
Injection
same class
CWE-74
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-19266 is "Kirachon context-engine review-git-diff Endpoint gitUtils.ts execGitCommand command injection", rated Medium. It affects Context-engine (Kirachon); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.