# CVE-2026-122019: 6amTech 6valley Social Login Flow existing-account-check existingAccountCheck authorization


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-v664-wmf2-px79

## What is CVE-2026-122019?

CVE-2026-122019 is a medium-severity vulnerability in 6amTech 6valley, published on 4 Nov 2026. 

### Official description

A vulnerability was identified in 6amTech 6valley 16.0. Impacted is the function existingAccountCheck of the file /api/v1/auth/existing-account-check of the component Social Login Flow. Such manipulation of the argument user_response leads to authorization bypass. The attack may be launched remotely. The exploit is publicly available and might be used.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-122019 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122019 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122019 is a medium-severity vulnerability in 6amTech 6valley, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122019 exists.

Affected product: 6amTech 6valley. 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-122019/ (Markdown: https://insights.sbomify.com/CVE-2026-122019/index.md)
```

## Sources

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

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