CVE-2018-18667: The mintToken function of Pylon (PYLNT) aka PylonToken, an Ethereum token, has an integer overflow that allows
CVE-2018-18667 is a high-severity flaw (CVSS 7.5) affecting pylontoken. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The mintToken function of Pylon (PYLNT) aka PylonToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value, a related issue to CVE-2018-11812.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.4% (top 27%) |
| CISA exploited list | No |
| Weakness | CWE-190 |
| Published | 2018-12-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2018-18667?
pylontoken: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-18667 being exploited?
CVE-2018-18667 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-2018-18667 affect?
CVE-2018-18667 affects pylontoken. Severity is high (CVSS 7.5). The mintToken function of Pylon (PYLNT) aka PylonToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value, a related issue to CVE-2018-11812.
How urgent is CVE-2018-18667?
Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action