# CVE-2026-49447: Cosmos-Server's constellation public-devices endpoint accepts arbitrary bearer tokens

> Attackers can access Constellation device metadata by providing any non-empty bearer token, bypassing authentication checks in Cosmos-Server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-5fqm-cc34-fcf5, GO-2026-6124

## What is CVE-2026-49447?

CVE-2026-49447 is a medium-severity authentication bypass vulnerability in azukaar Cosmos-Server, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. In 0.22.18, `GET /cosmos/api/constellation/public-devices` discloses Constellation device metadata to a requester that supplies any non-empty Authorization header. The handler strips the string Bearer  from the header but never validates the resulting token and never uses it in the database query. This vulnerability is fixed in 0.22.19.

Weakness: CWE-287 (Improper Authentication)

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

3 open source packages ship an affected version, including github.com/azukaar/cosmos-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/azukaar/cosmos-server` | Go | From 0.22.18 | 0.22.19 |
| `github.com/azukaar/cosmos-server` | Go | From 0.22.18 | 0.22.19 |
| `github.com/azukaar/cosmos-server` | Go | From 0.22.18 | 0.22.19 |

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

Upgrade github.com/azukaar/cosmos-server to 0.22.19 or later.

## Is CVE-2026-49447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49447 is a medium-severity authentication bypass vulnerability in azukaar Cosmos-Server, published on 28 Jul 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-49447 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/azukaar/cosmos-server (Go): affected from 0.22.18; fixed in 0.22.19
- github.com/azukaar/cosmos-server (Go): affected from 0.22.18; fixed in 0.22.19
- github.com/azukaar/cosmos-server (Go): affected from 0.22.18; fixed in 0.22.19

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-49447/ (Markdown: https://insights.sbomify.com/CVE-2026-49447/index.md)
```

## Sources

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

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