dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-7961

MEDIUM · 6.9 CVSS v4.0 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in Wulkano KAP on MacOS allows TCC Bypass.This issue affects KAP: 3.6.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Code injection vulnerability in Wulkano KAP 3.6.0 on macOS allows an attacker to inject and execute arbitrary code, which can be used to bypass TCC (Transparency, Consent, and Control) security restrictions that govern application permissions on macOS.

MitigationUpdate to a patched version when available; until then, restrict KAP's permissions and network access, and monitor for suspicious behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm KAP is installed
    Check for the Wulkano KAP application in /Applications folder or via Spotlight search. On macOS, you can run: ls /Applications/ | grep -i kap or mdfind 'kMDItemFSName == "KAP"'
    Affected if KAP application is found on the system
  2. Identify installed KAP version
    Right-click KAP in Applications, select Get Info, or run: mdls -name kMDItemVersion /Applications/KAP.app 2>/dev/null || defaults read /Applications/KAP.app/Contents/Info.plist CFBundleShortVersionString 2>/dev/null
    Affected if Version is 3.6.0 (exact match to affected version)
  3. Check if KAP has TCC permissions granted
    Open System Preferences > Security & Privacy > Privacy tab. Review permissions for Accessibility, Automation, Full Disk Access, or other TCC categories. Or query: sqlite3 ~/Library/Application\ Support/com.apple.TCC/TCC.db 'SELECT client,allowed FROM access WHERE client LIKE "%KAP%"' 2>/dev/null
    Affected if KAP has any TCC permissions enabled (Accessibility, Automation, Full Disk Access, etc.)
  4. Review KAP configuration for code injection vectors
    Examine KAP preferences or config files in ~/Library/Application\ Support/KAP/ for any unsigned scripts, external command paths, or plugin directories that could accept injected code
    Affected if Config allows execution of external scripts or contains suspicious entries

User is affected if Wulkano KAP version 3.6.0 is installed and has any TCC permissions granted, as the code injection flaw could enable bypass of those restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; until then, restrict KAP's permissions and network access, and monitor for suspicious behavior.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing5.0 h
  • Review / QA3.0 h
22.0 hours of engineering $3,890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7961 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data