# CVE-2026-42163: Auth bypass in n/a

> Attackers can bypass authentication via LTI to access internal accounts in Mahara, requiring specific LTI configurations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-f7jm-86g7-97p8

## What is CVE-2026-42163?

CVE-2026-42163 is a critical authentication bypass vulnerability in n/a, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mahara before 25.04.5 and 26.04.0 is vulnerable to unauthorized access to internal accounts via Learning Tools Interoperability (LTI) under certain circumstances. This applies to LTI 1.1 and LTI 1.3 Advantage.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-42163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42163 is a critical authentication bypass vulnerability in n/a, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42163 in the wild and no public exploit code.

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

## Sources

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

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