# CVE-2025-53947: Cognex In-Sight Explorer and In-Sight Camera Firmware Incorrect Default Permissions

> Local attackers can corrupt sensitive data due to weak default permissions on a data folder in Cognex In-Sight software.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 18 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-65x9-r46v-g944

## What is CVE-2025-53947?

CVE-2025-53947 is a medium-severity vulnerability in Cognex In-Sight 2000 series, published on 18 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local attacker with low privileges on the Windows system where the 
software is installed can exploit this vulnerability to corrupt 
sensitive data. A data folder is created with very weak privileges, 
allowing any user logged into the Windows system to modify its content.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2025-53947?


## How do I fix CVE-2025-53947?

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

## Is CVE-2025-53947 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53947 and fix it if it is affected.

What it is: CVE-2025-53947 is a medium-severity vulnerability in Cognex In-Sight 2000 series, published on 18 Sep 2025. 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-2025-53947 in the wild and no public exploit code.

Affected product: Cognex In-Sight 2000 series. 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-2025-53947/ (Markdown: https://insights.sbomify.com/CVE-2025-53947/index.md)
```

## Sources

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

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