NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2023-50658 — jose2go

MEDIUMFix: dvsekhvalnov/jose2go@a4584e9

CVE-2023-50658 is a medium-severity (CVSS 5.3) CWE-770 vulnerability in github.com/dvsekhvalnov/jose2go. A fix is available for github.com/dvsekhvalnov/jose2go — see the affected versions and patch details below.

jose2go vulnerable to denial of service via large p2c value

Also known asGHSA-6294-6rgp-fr7rGHSA-mhpq-9638-x6pwGO-2023-2409
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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 CVE-2023-50658.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.00%0.44%0.88%1.32%0.1%0.8%May 26Aug 26Nov 26

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

1 pkg affected
🐹github.com/dvsekhvalnov/jose2go

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

The jose2go component before 1.6.0 for Go allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/dvsekhvalnov/jose2goall versions1.6.0go get github.com/dvsekhvalnov/jose2go@v1.6.0

Affected Products

1 product · 1 configurations
Application
jose2godvsekhvalnov
< 1.6.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update github.com/dvsekhvalnov/jose2go to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50658 is resolved across your whole dependency graph.

  3. 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

The jose2go component before 1.6.0 for Go allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.
O3 Security · Impact-Aware SCA

Is CVE-2023-50658 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2023-50658: jose2go DoS — Fixed in 1.6.0