# CVE-2026-124621: A vulnerability was determined in kongxin-github Java_Library_Management_System up to 70a6eb6b96fe64575d8051f1a59055bfc5dc5885.


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

## What is CVE-2026-124621?

CVE-2026-124621 is a medium-severity vulnerability in kongxin-github Java_Library_Management_System, published on 9 Nov 2026. 

### Official description

A vulnerability was determined in kongxin-github Java_Library_Management_System up to 70a6eb6b96fe64575d8051f1a59055bfc5dc5885. This affects the function UpdateAdmin.deleteuser/UpdateAdmin.updateadmin/UpdateAdmin.updatepass/Book.addbook/Book.modifybook/Book.deletebook/Category.addcategory/Category.setcategory/Landing.sureadmin of the file src/view/MainInterface.java of the component Swing UI Layer. This manipulation causes improper authorization. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-124621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124621 is a medium-severity vulnerability in kongxin-github Java_Library_Management_System, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124621 exists.

Affected product: kongxin-github Java_Library_Management_System. 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-124621/ (Markdown: https://insights.sbomify.com/CVE-2026-124621/index.md)
```

## Sources

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

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