CVE-2021-29451 is a critical-severity (CVSS 9.1) CWE-347 vulnerability in com.manydesigns:portofino-dispatcher. A fix is available for com.manydesigns:portofino-dispatcher — see the affected versions and patch details below.
Missing validation of JWT signature in `ManyDesigns/Portofino`
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-29451 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.manydesigns:portofino-dispatcher☕com.manydesigns:portofino-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Portofino is an open source web development framework. Portofino before version 5.2.1 did not properly verify the signature of JSON Web Tokens. This allows forging a valid JWT.
Patches
The issue will be patched in the upcoming 5.2.1 release.
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/ManyDesigns/Portofino
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.manydesigns:portofino-dispatcher | ≥ 5.0.0&&< 5.2.1 | 5.2.1com.manydesigns:portofino-dispatcher:5.2.1 |
| ☕Maven | com.manydesigns:portofino-core | ≥ 5.0.0&&< 5.2.1 | 5.2.1com.manydesigns:portofino-core:5.2.1 |
Affected Products
portofinomanydesignsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.manydesigns:portofino-dispatcher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.manydesigns:portofino-dispatcher to 5.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29451 is resolved across your whole dependency graph.
Workarounds
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.
Frequently Asked Questions
Is CVE-2021-29451 in your dependencies?
Find it across Maven, including transitive dependencies.