CVE-2025-11130
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 · uneditedA weakness has been identified in iHongRen pptp-vpn 1.0/1.0.1 on macOS. This issue affects the function shouldAcceptNewConnection of the file HelpTool/HelperTool.m of the component XPC Service. This manipulation causes missing authentication. The attack can only be executed locally. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA missing authentication vulnerability exists in the XPC service helper tool (HelpTool/HelperTool.m) of iHongRen pptp-vpn on macOS. The shouldAcceptNewConnection function fails to properly authenticate incoming XPC connection requests, allowing local attackers to bypass authorization and interact with the privileged helper tool without credentials. This local privilege escalation could enable code execution in the context of the helper 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check if iHongRen pptp-vpn software is installedSearch for iHongRen or pptp-vpn related files, folders, or installed applications on the system. Check common installation directories and the system's list of installed programs.Affected if The iHongRen pptp-vpn application or its components are found on the system.
-
Identify running processes related to iHongRen pptp-vpnUse task manager, ps, or similar process listing tools to look for iHongRen, pptp-vpn, or HelperTool related processes. Also check for any XPC service processes running on the system.Affected if Processes named HelperTool, iHongRen, pptp-vpn, or related VPN services are actively running.
-
Locate the HelpTool componentSearch the filesystem for the HelperTool.m file or compiled HelperTool binary in the iHongRen installation directory, typically under a HelpTool or similar subfolder within the application's installation path.Affected if The HelperTool component file or binary exists in the iHongRen pptp-vpn installation directory.
-
Verify XPC service configurationCheck system launch items, services, or daemon configurations for any entries related to iHongRen pptp-vpn XPC service that would auto-start the vulnerable component.Affected if The XPC service is configured to start automatically or is currently enabled on the system.
The system is affected if the iHongRen pptp-vpn software is installed and the HelpTool XPC service component is present or running, as this is where the shouldAcceptNewConnection authentication bypass exists.
Generated from the published advisory. Verify against your own configuration.
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 dataSince the vendor did not respond, users should consider removing the vulnerable helper tool if possible, deploy macOS endpoint protection, and restrict local access to the system. Alternative VPN solutions from responsive vendors are recommended until a patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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