How severe is GHSA-j4rh-7jcr-qm69?

No CVSS score has been assigned to GHSA-j4rh-7jcr-qm69 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j4rh-7jcr-qm69?

GHSA-j4rh-7jcr-qm69 affects the following packages: misp-modules (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-j4rh-7jcr-qm69?

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.

How do I detect GHSA-j4rh-7jcr-qm69 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for misp-modules, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j4rh-7jcr-qm69 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-j4rh-7jcr-qm69?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j4rh-7jcr-qm69 can be triaged on real exposure rather than presence alone.

Is GHSA-j4rh-7jcr-qm69 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j4rh-7jcr-qm69 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j4rh-7jcr-qm69?

GHSA-j4rh-7jcr-qm69 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j4rh-7jcr-qm69?

GHSA-j4rh-7jcr-qm69 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j4rh-7jcr-qm69 published, and has it been updated?

GHSA-j4rh-7jcr-qm69 was published on May 6, 2026 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-j4rh-7jcr-qm69 — misp-modules

Fix: MISP/misp-modules@52cda9c

GHSA-j4rh-7jcr-qm69 is a Cross-Site Request Forgery (CSRF) vulnerability in misp-modules. No vendor fix is recorded yet; mitigation options are listed below.

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

See advisory

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j4rh-7jcr-qm69.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

MISP modules are autonomous modules that can be used to extend MISP for new services. In 3.0.7 and earlier, 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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`misp-modules`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for misp-modules, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j4rh-7jcr-qm69 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-j4rh-7jcr-qm69 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works