Cosmos-Server's constellation public-devices endpoint accepts arbitrary bearer tokens
CVE-2026-49447GHSA-5fqm-cc34-fcf5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/azukaar/cosmos-server 0.22.19), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/azukaar/cosmos-server
- Affected
- >= 0.22.18, <= 0.22.18
- Fixed in
- 0.22.19
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5fqm-cc34-fcf5 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <0.22.19 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6124 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <0.22.19 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5fqm-cc34-fcf5 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <=0.22.18
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-49447: 0.38% estimated exploitation activity in the next 30 days; percentile 32.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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 was confirmed locally by routing a request through the real tokenMiddleware with Authorization: Bearer not-a-real-token. The request returned public Constellation device metadata from a disposable fixture. A missing-header negative control returned 401 Unauthorized, proving the bypass is specifically the acceptance of arbitrary bearer values. Details Source-to-sink path: - src/httpServer.go:690 registers /api/constellation/public-devices on the authenticated admin API router. - src/httpServer.go:815-817 applies SecureAPI(..., public=false, ...), which runs tokenMiddleware. - src/httpServer.go:231-237 only treats Authorization: Bearer cosmos... as a Cosmos API token for validation. Other…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-5fqm-cc34-fcf5
- Revision 2 · amended ·
Amended from osv record GO-2026-6124
- Revision 1 · created ·
Published from osv record GHSA-5fqm-cc34-fcf5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-49447 Advisory: Cosmos-Server's constellation public-devices endpoint accepts arbitrary bearer tokens IDs: CVE-2026-49447, GHSA-5fqm-cc34-fcf5 Record: https://patchnext.com/advisories/cve-2026-49447 (revision 3, source checked 26 Oct 2026, 15:27 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/azukaar/cosmos-server 0.22.19. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/azukaar/cosmos-server: affected >= 0.22.18, <= 0.22.18; fixed in 0.22.19 ## Suggested inspection (read-only) - Go github.com/azukaar/cosmos-server: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/azukaar/cosmos-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-5fqm-cc34-fcf5 (OSV record GHSA-5fqm-cc34-fcf5 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <0.22.19 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6124 (OSV record GO-2026-6124 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <0.22.19 (fixed)) - Verified: https://github.com/advisories/GHSA-5fqm-cc34-fcf5 (GitHub-reviewed advisory GHSA-5fqm-cc34-fcf5 lists affected ranges: Go github.com/azukaar/cosmos-server >=0.22.18 <=0.22.18) Commands are suggestions: review each one before running it.
Loading voting…