Vulnerability Database · npm · @orpc/openapi · Version
@orpc/openapi 0.0.0-next.6a3f818
0.0.0-next.6a3f818 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 09 Apr 2026
Licence MIT
Also known from other sources 1
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
@orpc/openapi 0.0.0-next.6a3f818 vulnerabilities
1 vulnerability cover @orpc/openapi 0.0.0-next.6a3f818. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-33331: Stored XSS Vulnerability in @orpc/openapi via Unescaped JSON.stringify | 8.2 high | 1.13.9 | 20 Mar 2026 |
Looking for another version, or everything Vulert holds for @orpc/openapi?
Questions
About @orpc/openapi 0.0.0-next.6a3f818
Is @orpc/openapi 0.0.0-next.6a3f818 vulnerable?
Yes. 1 vulnerability in the Vulert database cover @orpc/openapi 0.0.0-next.6a3f818: 0 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.0-next.6a3f818 the latest release of @orpc/openapi?
No. 0.0.0-next.6a3f818 was published 09 Apr 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor @orpc/openapi for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @orpc/openapi version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.