Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-1000207: A vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functi

50
This month
HIGH 8.8UPGRADEUPGRADE

CVE-2017-1000207 is a high-severity flaw (CVSS 8.8) affecting swagger-codegen, swagger-parser. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particular, affects the 'generate' and 'validate' command in swagger-codegen (<= 2.2.2) and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance1.6% (top 24%)
CISA exploited listNo
WeaknessCWE-502
Published2017-11-27
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: swagger

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

swagger swagger-codegen UPGRADE
Affected: <= 2.2.2
Fixed in: newer than 2.2.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy swagger-codegen || rpm -q swagger-codegen || swagger-codegen --version
2. UPGRADE to newer than 2.2.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade swagger-codegen
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade swagger-codegen
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
swagger swagger-parser UPGRADE
Affected: <= 1.0.30
Fixed in: newer than 1.0.30
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy swagger-parser || rpm -q swagger-parser || swagger-parser --version
2. UPGRADE to newer than 1.0.30 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade swagger-parser
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade swagger-parser
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-1000207?

swagger-codegen: upgrade to newer than 2.2.2; swagger-parser: upgrade to newer than 1.0.30. Exact commands for each OS are on this page.

Is CVE-2017-1000207 being exploited?

CVE-2017-1000207 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-1000207 affect?

CVE-2017-1000207 affects swagger-codegen, swagger-parser. Severity is high (CVSS 8.8). A vulnerability in Swagger-Parser's version <= 1.0.30 and Swagger codegen version <= 2.2.2 yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This in particu

How urgent is CVE-2017-1000207?

Priority 50/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.