# CVE-2026-1612: Hard-coded AWS Key in AL-KO Robolinho Update Software

> Hard-coded AWS keys in AL-KO Robolinho Update Software allow attackers to read data from the vendor's AWS bucket.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-7x64-vh67-7fgv

## What is CVE-2026-1612?

CVE-2026-1612 is a medium-severity vulnerability in AL-KO Robolinho Update Software, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AL-KO Robolinho Update Software has hard-coded AWS Access and Secret keys that allow anyone to access AL-KO's AWS bucket. Using the keys directly might give the attacker greater access than the app itself. Key grants AT LEAST read access to some of the objects in bucket.

The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only versions 8.0.21.0610 and 8.0.22.0524 were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

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

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


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

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

## Is CVE-2026-1612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1612 is a medium-severity vulnerability in AL-KO Robolinho Update Software, published on 30 Mar 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-1612 in the wild and no public exploit code.

Affected product: AL-KO Robolinho Update Software. 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-1612/ (Markdown: https://insights.sbomify.com/CVE-2026-1612/index.md)
```

## Sources

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

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