# CVE-2026-43510: CISA manage.get.gov insecure portfolio administrative privileges

> An organization administrator can improperly assign domain manager privileges to domains outside their organization, requiring an upgrade to fix.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-6wrg-x3j6-x464

## What is CVE-2026-43510?

CVE-2026-43510 is a medium-severity vulnerability in CISA manage.get.gov, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-43510?


## How do I fix CVE-2026-43510?

No fix has been published for CVE-2026-43510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43510 being exploited?

There is no known exploitation of CVE-2026-43510 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43510 and fix it if it is affected.

What it is: CVE-2026-43510 is a medium-severity vulnerability in CISA manage.get.gov, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43510 in the wild and no public exploit code.

Affected product: CISA manage.get.gov. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43510/ (Markdown: https://insights.sbomify.com/CVE-2026-43510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43510
- OSV: https://osv.dev/vulnerability/CVE-2026-43510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43510/
Summaries are generated and may contain mistakes; the official description above is the record.