# CVE-2025-53813: TCC Bypass via misconfigured Node fuses in Nozbe

> Local attackers can bypass macOS TCC permissions in Nozbe due to misconfigured Node fuses, executing code with inherited user-granted access.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/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:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-r4cg-2rhj-cv67

## What is CVE-2025-53813?

CVE-2025-53813 is a medium-severity vulnerability in Nozbe, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The configuration of Nozbe on macOS, specifically the "RunAsNode" fuse enabled, allows a local attacker with unprivileged access to execute arbitrary code that inherits Nozbe TCC (Transparency, Consent, and Control) permissions. 
Acquired resource access is limited to previously granted permissions by the user. Access to other resources beyond granted-permissions requires user interaction with a system prompt asking for permission.

This issue was fixed in version 2025.11 of Nozbe.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2025-53813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53813 is a medium-severity vulnerability in Nozbe, published on 26 Aug 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-53813 in the wild and no public exploit code.

Affected product: Nozbe. 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-53813/ (Markdown: https://insights.sbomify.com/CVE-2025-53813/index.md)
```

## Sources

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

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