# CVE-2026-123618: ABP Framework before 10.7.1 Authentication Bypass via External Login Provider


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-xh2v-vqcx-cgpj

## What is CVE-2026-123618?

CVE-2026-123618 is a high-severity vulnerability in abpframework abp, published on 6 Nov 2026. 

### Official description

ABP Framework before 10.7.1 contains an authentication bypass vulnerability that skips account state and two-factor checks when password login succeeds through a registered IExternalLoginProvider. Attackers holding the external directory password for deactivated, locked, or 2FA-protected accounts can obtain valid access tokens from the /connect/token password grant.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-123618 being exploited?

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

Public exploit code:

- CVE-2026-123618 — the external login path in ABP skips the pre-sign-in gate and the second factor (github_poc): https://github.com/yuwkaaa/CVE-2026-123618

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123618 is a high-severity vulnerability in abpframework abp, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123618 in the wild and no public exploit code.

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

## Sources

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

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