How severe is GHSA-prjq-f4q3-fvfr?

GHSA-prjq-f4q3-fvfr has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-prjq-f4q3-fvfr?

GHSA-prjq-f4q3-fvfr affects the following packages: github.com/russellhaering/gosaml2 (Go), github.com/russellhaering/goxmldsig (Go). Ecosystems affected: Go.

How do I fix GHSA-prjq-f4q3-fvfr?

Update github.com/russellhaering/gosaml2 to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prjq-f4q3-fvfr is resolved across your whole dependency graph.

How do I detect GHSA-prjq-f4q3-fvfr in my Go dependencies?

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

How do I mitigate GHSA-prjq-f4q3-fvfr if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-prjq-f4q3-fvfr actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-prjq-f4q3-fvfr, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-prjq-f4q3-fvfr?

GHSA-prjq-f4q3-fvfr has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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-prjq-f4q3-fvfr?

GHSA-prjq-f4q3-fvfr is classified as NULL Pointer Dereference (CWE-476). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-prjq-f4q3-fvfr published, and has it been updated?

GHSA-prjq-f4q3-fvfr was published on November 15, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

github.com/russellhaering/gosaml2 is vulnerable to NULL Pointer DereferenceGHSA-prjq-f4q3-fvfr

HIGHFix: russellhaering/gosaml2#90

GHSA-prjq-f4q3-fvfr is a high-severity (CVSS 7.5) NULL Pointer Dereference vulnerability in github.com/russellhaering/gosaml2. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/russellhaering/gosaml2 — see the affected versions and patch details below.

Also known asCVE-2020-7711 CVE-2020-7731 GHSA-gq5r-cc4w-g8xf GHSA-mqqv-chpx-vq25GO-2020-0046SNYK-GOLANG-GITHUBCOMRUSSELLHAERINGGOSAML2-608302

Published

Nov 15, 2022

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹github.com/russellhaering/gosaml2🐹github.com/russellhaering/goxmldsig

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

Description

Impact

In versions prior to v0.7.0 it was possible for an attacker to supply an invalid assertion which would trigger a panic due to a nil-pointer dereference.

Patches

The issue was patched in v0.7.0, released on March 2, 2022.

Workarounds

Callers to gosaml2 can use recover() to handle panics to mitigate a potential DoS.

References

See issue #59 for details.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/russellhaering/gosaml2`	all versions	0.7.0`go get github.com/russellhaering/gosaml2@v0.7.0`
🐹Go	`github.com/russellhaering/goxmldsig`	all versions	1.1.1`go get github.com/russellhaering/goxmldsig@v1.1.1`

Affected Products

1 product · 1 configurations

Application

goxmldsiggoxmldsig_project

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

This affects all versions of package github.com/russellhaering/goxmldsig…

github.comNVDAug 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/russellhaering/gosaml2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/russellhaering/gosaml2 to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prjq-f4q3-fvfr is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact In versions prior to v0.7.0 it was possible for an attacker to supply an invalid assertion which would trigger a panic due to a nil-pointer dereference. ### Patches The issue was patched in v0.7.0, released on March 2, 2022. ### Workarounds Callers to `gosaml2` can use `recover()` to handle panics to mitigate a potential DoS. ### References See issue [#59](https://github.com/russellhaering/gosaml2/issues/59) for details.