How severe is CVE-2016-1000229?

CVE-2016-1000229 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-1000229?

CVE-2016-1000229 affects the following packages: swagger-ui (npm). Ecosystems affected: npm.

How do I fix CVE-2016-1000229?

Update swagger-ui to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000229 is resolved across your whole dependency graph.

How do I detect CVE-2016-1000229 in my npm dependencies?

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

How do I mitigate CVE-2016-1000229 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2016-1000229 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-1000229 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 CVE-2016-1000229?

CVE-2016-1000229 has an EPSS (Exploit Prediction Scoring System) score of 4.0%, placing it in the 91th 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 CVE-2016-1000229?

CVE-2016-1000229 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2016-1000229 published, and has it been updated?

CVE-2016-1000229 was published on December 20, 2019 and was last updated on April 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

CVE-2016-1000229 — swagger-ui

MEDIUM

CVE-2016-1000229 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in swagger-ui. A fix is available for swagger-ui — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in swagger-ui

Also known asGHSA-h8wp-wgcq-qhrf

Published

Dec 20, 2019

Updated

Apr 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% 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

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

167other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

swagger-uinpm

170Kdownloads / week

Description

swagger-ui has XSS in key names

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`swagger-ui`	all versions	2.2.1`npm install swagger-ui@2.2.1`

Affected Products

3 products · 3 configurations

Application

jboss fuseredhat

1 version

6.3

Application

openshiftredhat

1 version

2.0

Application

swagger-uismartbear

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swagger-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update swagger-ui to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000229 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

RHSA-2017:0868Red Hat JBoss A-MQ 6.3

Frequently Asked Questions

swagger-ui has XSS in key names

O3 Security · Impact-Aware SCA

Is CVE-2016-1000229 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

swagger-ui

7.2/10

Maintained10/10

Code-Review5/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Dec 20, 2019

Last updated

Apr 1, 2026

Identifiers

CVE-2016-1000229

GHSA-h8wp-wgcq-qhrf

References

Advisoryraw.githubusercontent.com · CVE 2016 1000229.json Advisorysecurityfocus.com Advisoryaccess.redhat.com · RHSA 2017:0868 Advisorynvd.nist.gov · CVE 2016 1000229 Reportbugzilla.redhat.com · show bug.cgi Packagegithub.com · swagger ui

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting swagger-ui are rated as high or higher (top: critical).

CVE-2018-25031GHSA-qrmm-w75w-3wpxGHSA-22q9-hqm5-mhmcGHSA-388g-jwpg-x6j4GHSA-4f9m-pxwh-68hgGHSA-vp93-gcx5-4w52GHSA-w992-2gmj-9xxjCVE-2016-1000226

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 1, 2026

CVE-2016-1000229 — swagger-ui

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2016-1000229 in your dependencies?