manage.get.gov is the .gov TLD registrar maintained by CISA. manage.get.gov allows an organization administrator to assign domain manager privileges for domains not already in another organization. Fixed in 1.176.0 on or around 2026-04-30.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43510 affects CISA's manage.get.gov registrar platform. A highly privileged organization administrator could assign domain manager rights for domains that were not already in another organization. That could create improper administrative control over .gov domain management. The bundle says it was fixed in version 1.176.0 around April 30, 2026.
Executive priority
Treat this as a moderate governance and domain-control risk. Prioritize confirmation that the fixed release is deployed and that no improper domain management permissions were assigned before the fix.
Technical view
The issue is classified as CWE-266 and scored CVSS 3.1 5.9 with AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H. The flaw concerns insecure portfolio administrative privileges in manage.get.gov, allowing an organization administrator to assign domain manager privileges outside the intended ownership boundary when a domain is not already associated with another organization.
Likely exposure
Exposure appears limited to CISA manage.get.gov and users with organization administrator privileges. The source bundle does not establish broader affected products, public exploit availability, or a precise vulnerable version range beyond the stated fix in 1.176.0.
Exploitation context
CISA KEV status is false, and the provided sources do not state active exploitation. Practical abuse appears constrained by the need for high privileges and high attack complexity, but the business impact can be material if domain management authority is improperly assigned.
Researcher notes
Evidence supports an authorization-boundary issue, not remote unauthenticated compromise. The bundle names the affected product, CWE, CVSS vector, advisory, patch pull request, release notes, issue, and CSAF source, but it does not provide exploit details or active exploitation evidence.
Mitigation direction
Confirm manage.get.gov is running version 1.176.0 or later.
Review the GitHub advisory and release notes for vendor guidance.
Restrict organization administrator roles to trusted, current personnel.
Audit domain manager assignments for unexpected or unauthorized changes.
Review administrative logs around the pre-fix period.
Validation and detection
Inventory manage.get.gov version and deployment date.
Check whether any organization administrators held unnecessary privileges.
Review audit logs for unusual domain manager assignment events.
Validate current domain-to-organization ownership mappings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-266 · source CWE mapping
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.