# CVE-2026-11970: Security feature bypass in F1E mac

> A normal user can disable the Safari extension to bypass Data Loss Prevention protections in Forcepoint One Endpoint for macOS.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-6vvx-c6w6-g33q

## What is CVE-2026-11970?

CVE-2026-11970 is a medium-severity vulnerability in Forcepoint F1E mac, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows a normal (non-admin) user to disable the Forcepoint One Endpoint SafariExtension and bypass DLP protection in F1E Mac OS before v26.04.5758.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2026-11970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11970 is a medium-severity vulnerability in Forcepoint F1E mac, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11970 in the wild and no public exploit code.

Affected product: Forcepoint F1E mac. 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-11970/ (Markdown: https://insights.sbomify.com/CVE-2026-11970/index.md)
```

## Sources

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

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