# CVE-2006-4886: Race condition in n/a

> Local privileged users can bypass security restrictions and disable On-Access Scan via a race condition in the user interface.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x7j6-25gq-8h9f

## What is CVE-2006-4886?

CVE-2006-4886 is a low-severity vulnerability in n/a, published on 19 Sep 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The VirusScan On-Access Scan component in McAfee VirusScan Enterprise 7.1.0 and Scan Engine 4.4.00 allows local privileged users to bypass security restrictions and disable the On-Access Scan option by opening the program via the task bar and quickly clicking the Disable button, possibly due to an interface-related race condition.

## Which versions are affected by CVE-2006-4886?

It affects 2 products.


Products: Mcafee Scan Engine, Mcafee Virusscan Enterprise.

## How do I fix CVE-2006-4886?

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

## Is CVE-2006-4886 being exploited?

There is no known exploitation of CVE-2006-4886 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4886 and fix it if it is affected.

What it is: CVE-2006-4886 is a low-severity vulnerability in n/a, published on 19 Sep 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-4886 in the wild and no public exploit code.

Affected product: n/a. 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-2006-4886/ (Markdown: https://insights.sbomify.com/CVE-2006-4886/index.md)
```

## Sources

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

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