# CVE-2026-19193: Jiangmin Antivirus Minifilter Port kvcore.sys MessageNotifyCallback access control

> Local attackers can exploit improper access controls in the Jiangmin Antivirus kernel driver to escalate privileges.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-rr8j-hjqf-g6cv

## What is CVE-2026-19193?

CVE-2026-19193 is a high-severity missing authorization vulnerability in Jiangmin Antivirus, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in Jiangmin Antivirus 21. Impacted is the function MessageNotifyCallback in the library kvcore.sys of the component Minifilter Port. Executing a manipulation can lead to improper access controls. The attack needs to be launched locally. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-19193?


## How do I fix CVE-2026-19193?

No fix has been published for CVE-2026-19193 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19193 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19193 exists.

Public exploit code:

- CVE-2026-19193 Proof of Concept (github_poc): https://github.com/patrickt2017/CVE-2026-19193-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19193 and fix it if it is affected.

What it is: CVE-2026-19193 is a high-severity missing authorization vulnerability in Jiangmin Antivirus, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19193 exists.

Affected product: Jiangmin Antivirus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19193/ (Markdown: https://insights.sbomify.com/CVE-2026-19193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19193
- OSV: https://osv.dev/vulnerability/CVE-2026-19193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19193/
Summaries are generated and may contain mistakes; the official description above is the record.