# CVE-2026-68490: Information disclosure in cPanel

> Local users can access sensitive CalDAV and CardDAV data from other accounts due to incorrect permission assignments in cPanel.

- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 23 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-3mfr-vp2j-wj65

## What is CVE-2026-68490?

CVE-2026-68490 is a high-severity vulnerability in WebPros cPanel, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect permission assignment allows local users to obtain sensitive CalDAV/CardDAV information belonging to other accounts.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-68490?


## How do I fix CVE-2026-68490?

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

## Is CVE-2026-68490 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68490 and fix it if it is affected.

What it is: CVE-2026-68490 is a high-severity vulnerability in WebPros cPanel, published on 23 Sep 2026. 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-2026-68490 in the wild and no public exploit code.

Affected product: WebPros cPanel. 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-2026-68490/ (Markdown: https://insights.sbomify.com/CVE-2026-68490/index.md)
```

## Sources

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

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