# CVE-2026-123664: nasa-gcn gcn.nasa.gov Email Notification email improper authorization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-r6mw-j6c7-mgp2

## What is CVE-2026-123664?

CVE-2026-123664 is a medium-severity vulnerability in nasa-gcn gcn.nasa.gov, published on 6 Nov 2026. 

### Official description

A security flaw has been discovered in nasa-gcn gcn.nasa.gov up to b299b562af665878964b981a459f0a9c04b11adf. This issue affects some unknown processing of the file /user/email of the component Email Notification Handler. Performing a manipulation of the argument Recipient results in improper authorization. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The pull request to fix this issue awaits acceptance.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-123664 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123664 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123664 is a medium-severity vulnerability in nasa-gcn gcn.nasa.gov, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123664 exists.

Affected product: nasa-gcn gcn.nasa.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-123664/ (Markdown: https://insights.sbomify.com/CVE-2026-123664/index.md)
```

## Sources

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

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