Skip to main content
VulnerabilityPublished

CVE-2026-55391: koxudaxi datamodel-code-generator · Reliance on Reverse DNS Resolution for a Security-Critical Action

Affects koxudaxi datamodel-code-generatorSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 0.63.0 soon.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.63.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade koxudaxi datamodel-code-generator to 0.63.0.

Affected software

ProductAffectedFixed in
koxudaxidatamodel-code-generatorAffected
  • <0.63.0
Fixed in
  • 0.63.0

AI-suggested

Upgrade datamodel-code-generator to version 0.63.0 or later, where this vulnerability is fixed. No other mitigation is indicated in the vendor advisory. Patch status is not explicitly stated but the fix is included in version 0.63.0.

Description

CVE-2026-55391 is a high-severity vulnerability in koxudaxi datamodel-code-generator versions prior to 0.63.0. The tool improperly relies on reverse DNS resolution for security-critical decisions, allowing DNS rebinding attacks to bypass network restrictions and potentially access internal services. This issue is fixed in version 0.63.0.

References

Community reviews

Loading reviews…