# CVE-2026-63239: Hard-coded AWS IAM credentials vulnerability

> Hard-coded AWS credentials in Koollab LMS allow attackers to access S3 buckets and SQS queues, exposing data and enabling malicious actions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-4fpv-9r28-747f

## What is CVE-2026-63239?

CVE-2026-63239 is a medium-severity vulnerability in Three Learning Koollab LMS, published on 29 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A hard-coded AWS IAM credentials vulnerability
in Koollab LMS allowed
an attacker to access shared multi-tenant S3 buckets and SQS queues, exposing
sensitive data and enabling malicious content injection, job manipulation, or
email interception.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-63239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63239 is a medium-severity vulnerability in Three Learning Koollab LMS, published on 29 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-63239 in the wild and no public exploit code.

Affected product: Three Learning Koollab LMS. 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-63239/ (Markdown: https://insights.sbomify.com/CVE-2026-63239/index.md)
```

## Sources

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

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