# CVE-2026-109412: Information disclosure in Neurons Patch for Intune

> A remote authenticated attacker can leak sensitive authentication information via an exposed dangerous endpoint in Ivanti Neurons Patch for Intune.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-4j6p-29h2-w33f

## What is CVE-2026-109412?

CVE-2026-109412 is a critical vulnerability in Ivanti Neurons Patch for Intune, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exposed dangerous endpoint in Ivanti Neurons Patch for Intune allows a remote authenticated attacker to leak sensitive authentication information.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-109412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109412 is a critical vulnerability in Ivanti Neurons Patch for Intune, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109412 in the wild and no public exploit code.

Affected product: Ivanti Neurons Patch for Intune. 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-109412/ (Markdown: https://insights.sbomify.com/CVE-2026-109412/index.md)
```

## Sources

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

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