dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-1078

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/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
A vulnerability has been found in AppHouseKitchen AlDente Charge Limiter up to 1.29 on macOS and classified as critical. This vulnerability affects the function shouldAcceptNewConnection of the file com.apphousekitchen.aldente-pro.helper of the component XPC Service. The manipulation leads to improper authorization. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. Upgrading to version 1.30 is able to address this issue. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure and acted very professional.

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 · high confidence

The vulnerability exists in the XPC service helper (com.apphousekitchen.aldente-pro.helper) of AlDente Charge Limiter for macOS. The shouldAcceptNewConnection function has improper authorization checks, allowing a local attacker to bypass authorization in the XPC service communication.

MitigationUpgrade AlDente Charge Limiter to version 1.30 or later to resolve the improper authorization vulnerability in the XPC service.

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Check installed AlDente version
    Run: defaults read "/Applications/AlDente Charge Limiter.app/Contents/Info" CFBundleShortVersionString or right-click app in Finder > Get Info > Version
    Affected if Version is lower than 1.30 (e.g., 1.29.x, 1.28.x, etc.)
  2. Verify XPC helper service exists
    Run: ls -la /Applications/AlDente\ Charge\ Limiter.app/Contents/Library/LaunchServices/ for com.apphousekitchen.aldente-pro.helper or check via launchctl list | grep aldente
    Affected if The helper daemon (com.apphousekitchen.aldente-pro.helper) is installed and running on the system
  3. Confirm XPC service is enabled
    Run: launchctl list | grep -i aldente to see if the helper is loaded, or check System Settings > General > Login Items for AlDente helper
    Affected if The AlDente helper is set to run at login (even if not actively charging, the XPC service may be listening)
  4. Check for prior versions
    Run: ls /Applications/ | grep -i aldente to see if older installer versions remain, or check ~/Library/Application Support/AlDente for version history
    Affected if Multiple AlDente versions are present or version cannot be definitively determined

If AlDente Charge Limiter version is below 1.30 and the XPC helper service (com.apphousekitchen.aldente-pro.helper) is installed/enabled, the system is vulnerable to authorization bypass in XPC communication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AlDente Charge Limiter to version 1.30 or later to resolve the improper authorization vulnerability in the XPC service.

Recommended fix High confidence

1.30

  1. Check current installed version of AlDente Charge Limiter
  2. Download AlDente Charge Limiter version 1.30 from the official vendor (AppHouseKitchen)
  3. Install the update following standard macOS application update procedures
  4. Verify the new version (1.30) is installed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1078 — 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-1078 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