Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI
Not in CISA KEV

GHSA-j4rh-7jcr-qm69

Fix: MISP/misp-modules@52cda9c

GHSA-j4rh-7jcr-qm69 is a security vulnerability in misp-modules. O3 Security confirms whether GHSA-j4rh-7jcr-qm69 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

misp-modules website - Missing CSRF protection in the website home blueprint

Also known asCVE-2026-44364PYSEC-2026-414
Published
May 6, 2026
Updated
Jun 29, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Jun 29, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍misp-modules

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A Cross-Site Request Forgery vulnerability in the MISP Modules website allowed an attacker to cause an authenticated user to submit unintended requests to the home endpoint. The vulnerability was due to the home blueprint being exempted from CSRF protection. This could allow modification of session query data in the context of the authenticated user. The issue was fixed by enabling CSRF protection for the affected blueprint and hardening query parsing. As reported by Bilal Teke.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐍PyPImisp-modulesall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for misp-modules. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of misp-modules has shipped for GHSA-j4rh-7jcr-qm69 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-j4rh-7jcr-qm69 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j4rh-7jcr-qm69. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A Cross-Site Request Forgery vulnerability in the MISP Modules website allowed an attacker to cause an authenticated user to submit unintended requests to the home endpoint. The vulnerability was due to the home blueprint being exempted from CSRF protection. This could allow modification of session query data in the context of the authenticated user. The issue was fixed by enabling CSRF protection for the affected blueprint and hardening query parsing. As reported by Bilal Teke.
O3 Security · Impact-Aware SCA

Is GHSA-j4rh-7jcr-qm69 in your dependencies?

O3 detects GHSA-j4rh-7jcr-qm69 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.