# CVE-2025-41363: CORS vulnerability in IDF and ZLF

> Authenticated attackers can bypass CORS restrictions on ZIV IDF and ZLF devices to execute commands with view permissions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-q2fw-2q69-qh7p

## What is CVE-2025-41363?

CVE-2025-41363 is a medium-severity vulnerability in ZIV IDF and ZLF, published on 6 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In IDF v0.10.0-0C03-03 and ZLF v0.10.0-0C03-04, a configuration error has been detected in cross-origin resource sharing (CORS). Exploiting this vulnerability requires authenticating to the device and executing certain commands that can be executed with view permission.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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


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

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

## Is CVE-2025-41363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41363 is a medium-severity vulnerability in ZIV IDF and ZLF, published on 6 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41363 in the wild and no public exploit code.

Affected product: ZIV IDF and ZLF. 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-41363/ (Markdown: https://insights.sbomify.com/CVE-2025-41363/index.md)
```

## Sources

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

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