# CVE-2024-46636: SQL injection in n/a

> An attacker can exploit a SQL injection vulnerability in the category parameter of NASA EOSDIS MODAPS to read or modify database contents.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 28 Apr 2026

## What is CVE-2024-46636?

CVE-2024-46636 is a critical SQL injection vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NASA Earth Observing System Data and Information System (EOSDIS) MODAPS v8.1 was discovered to contain a SQL injection vulnerability in the category parameter

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-46636?


## How do I fix CVE-2024-46636?

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

## Is CVE-2024-46636 being exploited?

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

Public exploit code:

- SQL Injection vulnerability in NASA EOSDIS MODAPS due to improper input validation in the `category` parameter. This flaw allows attackers to manipulate backend SQL queries, potentially leading to unauthorized data access and database compromise. (github_poc): https://github.com/NU1L0/CVE-2024-46636-SQLi-MODAPS

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46636 and fix it if it is affected.

What it is: CVE-2024-46636 is a critical SQL injection vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-46636 in the wild and no public exploit code.

Affected product: n/a. 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-2024-46636/ (Markdown: https://insights.sbomify.com/CVE-2024-46636/index.md)
```

## Sources

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

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