CVE-2026-71254 (GCVE-0-2026-71254)
Vulnerability from cvelistv5 – Published: 2026-08-05 11:44 – Updated: 2026-08-10 11:46| URL | Tags |
|---|---|
| https://github.com/debevv/nanoMODBUS | third-party-advisory |
| https://github.com/debevv/nanoMODBUS/blob/master/… | third-party-advisory |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| debevv | nanoMODBUS |
Affected:
0 , ≤ 1.23.0
(semver)
|
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-71254",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-05T12:29:36.579901Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:29:59.671Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "nanoMODBUS",
"programFiles": [
"nanomodbus.c"
],
"vendor": "debevv",
"versions": [
{
"lessThanOrEqual": "1.23.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Shukhratbek Uraiimov"
}
],
"datePublic": "2026-08-05T11:44:20.214Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003enanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request\u0027s record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them.\u003c/p\u003e"
}
],
"value": "nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request\u0027s record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-787",
"description": "CWE-787",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-10T11:46:13.975Z",
"orgId": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"shortName": "TuranSec"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://github.com/debevv/nanoMODBUS"
},
{
"tags": [
"third-party-advisory"
],
"url": "https://github.com/debevv/nanoMODBUS/blob/master/nanomodbus.c"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "nanoMODBUS Server-Side Out-of-Bounds Write in handle_read_file_record()"
}
},
"cveMetadata": {
"assignerOrgId": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"assignerShortName": "TuranSec",
"cveId": "CVE-2026-71254",
"datePublished": "2026-08-05T11:44:20.214Z",
"dateReserved": "2026-08-05T11:43:52.777Z",
"dateUpdated": "2026-08-10T11:46:13.975Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-71254",
"date": "2026-11-09",
"epss": "0.00553",
"percentile": "0.46476"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "nanoMODBUS",
"programFiles": [
"nanomodbus.c"
],
"vendor": "debevv",
"versions": [
{
"lessThanOrEqual": "1.23.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"source": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request\u0027s record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them."
},
{
"lang": "es",
"value": "nanoMODBUS hasta la v1.23.0 contiene una escritura fuera de l\u00edmites en la funci\u00f3n handle_read_file_record() del lado del servidor Modbus (FC 0x14, Lectura de Registro de Archivo) en nanomodbus.c. La funci\u00f3n valida que el tama\u00f1o total de la solicitud no exceda los 245 bytes y que la record_length de cada sub-solicitud sea como m\u00e1ximo 124, pero nunca valida el tama\u00f1o de respuesta ACUMULATIVO de todas las sub-solicitudes antes de procesarlas. El acumulador response_data_size se declara como uint8_t y se incrementa en 2 + record_length2 por cada una de hasta 35 sub-solicitudes; con 35 sub-solicitudes de record_length=124, la demanda acumulada es de 8750 bytes, lo que desborda el acumulador uint8_t. Un bucle posterior llama entonces a get_n(), una funci\u00f3n interna sin comprobaci\u00f3n de l\u00edmites, una vez por sub-solicitud para obtener un puntero al b\u00fafer de recepci\u00f3n msg.buf de 260 bytes y avanza el buf_idx interno hasta 248 bytes por llamada; swap_regs() luego escribe en ese puntero incondicionalmente. Una \u00fanica solicitud FC 0x14 manipulada de un cliente de red no autenticado puede causar que se escriban hasta ~8490 bytes fuera de los l\u00edmites m\u00e1s all\u00e1 del b\u00fafer de 260 bytes, corrompiendo la memoria adyacente en el proceso del servidor y llevando a denegaci\u00f3n de servicio o potencial ejecuci\u00f3n remota de c\u00f3digo, particularmente en objetivos embebidos/bare-metal sin protecci\u00f3n de memoria."
}
],
"id": "CVE-2026-71254",
"lastModified": "2026-10-24T15:10:00.190",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-71254",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-05T12:29:36.579901Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-08-05T12:18:57.600",
"references": [
{
"source": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"url": "https://github.com/debevv/nanoMODBUS"
},
{
"source": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"url": "https://github.com/debevv/nanoMODBUS/blob/master/nanomodbus.c"
}
],
"sourceIdentifier": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-787"
}
],
"source": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-71254",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-05T12:29:36.579901Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:29:55.464Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "nanoMODBUS",
"programFiles": [
"nanomodbus.c"
],
"vendor": "debevv",
"versions": [
{
"lessThanOrEqual": "1.23.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Shukhratbek Uraiimov"
}
],
"datePublic": "2026-08-05T11:44:20.214Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003enanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request\u0027s record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them.\u003c/p\u003e"
}
],
"value": "nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request\u0027s record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-787",
"description": "CWE-787",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-10T11:46:13.975Z",
"orgId": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"shortName": "TuranSec"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://github.com/debevv/nanoMODBUS"
},
{
"tags": [
"third-party-advisory"
],
"url": "https://github.com/debevv/nanoMODBUS/blob/master/nanomodbus.c"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "nanoMODBUS Server-Side Out-of-Bounds Write in handle_read_file_record()"
}
},
"cveMetadata": {
"assignerOrgId": "309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c",
"assignerShortName": "TuranSec",
"cveId": "CVE-2026-71254",
"datePublished": "2026-08-05T11:44:20.214Z",
"dateReserved": "2026-08-05T11:43:52.777Z",
"dateUpdated": "2026-08-10T11:46:13.975Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.