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.
CVE-2026-49447
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 30, 2026
Advisory Details (3)
Auto-updated Jul 28, 2026Release 0.22.19
Patch available: azukaar/Cosmos-Server v0.22.19
https://github.com/azukaar/Cosmos-Server/releases/tag/v0.22.19commit 59c561d686c8 (azukaar/Cosmos-Server)
Fix landed in azukaar/Cosmos-Server commit 59c561d686c8 — awaiting tagged release
https://github.com/azukaar/Cosmos-Server/commit/59c561d686c8f9843b3e092b50f6346c481d8bbfConstellation public-devices endpoint accepts arbitrary bearer tokens · Advisory · azukaar/Cosmos-Server · GitHub
https://github.com/azukaar/Cosmos-Server/security/advisories/GHSA-5fqm-cc34-fcf5Vendor Advisories for CVE-2026-49447(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/azukaar/cosmos-server | 0.22.18 | 0.22.19 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 20:14 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 14:55 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 14:20 UTCEG score recompute
- 2026-07-29 13:59 UTCEG score recompute
- 2026-07-28 21:26 UTCEG score recompute
- 2026-07-28 21:02 UTCEG score recompute
- 2026-07-28 21:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(5)
What is CVE-2026-49447?
When was CVE-2026-49447 disclosed?
Is CVE-2026-49447 actively exploited?
What is the CVSS score of CVE-2026-49447?
How do I remediate CVE-2026-49447?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49447
Is Your Infrastructure Affected by CVE-2026-49447?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.