Security readout for executives and security teams
Plain-English summary
Yamcs versions before 5.12.7 let any authenticated user view user and group information that should require administrative access. The exposed data includes usernames, superuser status, and group memberships. This is not a takeover bug, but it can weaken security by helping an insider or compromised account map privileged users.
Executive priority
Treat as a prompt maintenance update, not an emergency outage event. Prioritize systems with many users, shared operational access, or sensitive mission-control roles because the vulnerability reveals privilege structure useful for follow-on attacks.
Technical view
In yamcs-core IamApi.java, listUsers, getUser, listGroups, and getGroup did not enforce SystemPrivilege.ControlAccess. The issue is CWE-862, with CVSS 4.3: network-accessible, low complexity, low privileges required, no user interaction, confidentiality impact only. Sources state fixes are available in 5.12.7 and 5.13.0.
Likely exposure
Yamcs deployments running versions before 5.12.7 are exposed when authenticated low-privilege users can reach IAM API functionality. Exposure is higher where Yamcs accounts are broadly issued or accessible through shared operational environments.
Exploitation context
The provided sources do not state active exploitation, and the CVE is not marked KEV. Abuse requires authenticated access, but no special privileges beyond login are required. The main risk is reconnaissance of identities and privilege relationships.
Researcher notes
Evidence points to missing authorization checks in Yamcs IAM API methods and a confidentiality-only impact. The bundle names affected versions as below 5.12.7 and fixes in 5.12.7 and 5.13.0. No source in the bundle proves public exploitation.
Mitigation direction
- Upgrade Yamcs to 5.12.7, 5.13.0, or later.
- Restrict Yamcs access to trusted authenticated users until upgraded.
- Review vendor advisory and release notes before rollout.
- After upgrading, review exposed account and group data for sensitivity.
Validation and detection
- Inventory Yamcs versions and flag deployments before 5.12.7.
- Confirm low-privilege users cannot access IAM user or group information.
- Review logs for unexpected IAM API access by non-admin accounts.
- Check tests or release evidence for ControlAccess enforcement.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-44595 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4GitHub_MVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/yamcs/yamcs/security/advisories/GHSA-p2rj-mrmc-9w29CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/yamcs/yamcs/commit/0e12b518f103f24681299318a30a460fe4327b88CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/commit/e90099fba98e96214217c195b6a5b87b5f46e51cCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.