Skip to main content

Cosmos Server CVE-2026-49447

| EUVDEUVD-2026-50056 MEDIUM
Improper Authentication (CWE-287)
2026-07-28 GitHub_M GHSA-5fqm-cc34-fcf5
5.3
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send GET request with arbitrary Bearer token
  2. Exploit
    Bypass token validation in tokenMiddleware
  3. Impact
    Retrieve unauthorized Constellation device metadata

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The Constellation feature must be enabled (disabled by default in Cosmos Server), and there must be at least one non-blocked, non-invisible device registered in the database. The attack requires only network access and any non-empty Authorization header; no authentication credentials are needed. Limiting factors include the default disabled state of Constellation and the requirement for existing device registrations.

Impact

CVSS 5.3 (medium) with AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N indicates low confidentiality impact with no privilege or user interaction required. However, exploitation requires the Constellation feature to be enabled (disabled by default) and at least one device registered. No EPSS score or KEV listing is available, but a proof-of-concept is described in the vendor advisory, elevating risk for deployments with Constellation enabled. For default configurations, the exposure is limited, but misconfigured instances are easily exploitable.

Exploit ScenarioDerived

An attacker sends a GET request to /cosmos/api/constellation/public-devices with an arbitrary Authorization header (e.g., Bearer fake-token). The server bypasses validation and returns a JSON list of device names, IPs, and user nicknames. This can be performed remotely without authentication, exposing internal network topology.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 28, 2026

Authentication bypass in Cosmos Server 0.22.18 allows unauthenticated attackers to leak Constellation device metadata via the public-devices endpoint. The handler accepts any non-empty Authorization header but does not validate the bearer token, exposing device names, IPs, and role flags. Publicly available exploit code exists, but no active exploitation is reported; the vulnerability is patched in version 0.22.19.

RemediationAI

Upgrade to Cosmos Server version 0.22.19, which includes the fix (commit 59c561d686c8f9843b3e092b50f6346c481d8bbf and release v0.22.19). As a workaround, disable the Constellation feature if not required by setting the appropriate configuration option, or restrict network access to the /api/constellation/public-devices endpoint via a reverse proxy or firewall. Note that disabling Constellation may break remote access functionality for existing devices.

Affected VersionsENISA

Cosmos-Server 0.22.18

Affected Packages

go github.com/azukaar/cosmos-server fix: 0.22.19
euvd cosmos_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Cosmos Server is a self-hosted server manager with a Constellation VPN feature that securely connects devices. The endpoint /cosmos/api/constellation/public-devices is registered on the authenticated admin API router and undergoes tokenMiddleware which only validates tokens with a specific cosmos_ prefix. The handler strips the Bearer prefix but never validates the token, allowing any non-empty bearer value to bypass authentication (CWE-287 Improper Authentication). The flaw exists in src/constellation/api_devices_public.go where the handler queries all non-blocked, non-invisible devices without filtering by the stripped token.

Know when Cosmos Server gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Network-accessible, low complexity, unauthenticated, no user interaction.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE MEDIUM

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
niche self-hosted server manager
Threat Intel
1
1 sources
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor CIRCL GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy