CVE-2026-107245 (GCVE-0-2026-107245)
Vulnerability from cvelistv5 – Published: 2026-11-10 00:32 – Updated: 2026-11-10 00:32- CWE-121 - Stack Overflow
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Versa | VOS |
Affected:
21.1.1 , ≤ 21.2.3
(semver)
Affected: 22.1.2 , < July 2, 2026 (semver) Affected: 22.1.3 , < July 2, 2026 (semver) Affected: 22.1.4 , < July 2, 2026 (semver) Affected: 23.1.2 , < 23.1.2 (semver) Unaffected: 22.1.2 July-2-2026-Hotfix , < 22.1.2 July-2-2026-Hotfix (semver) Unaffected: 22.1.3 July-2-2026-Hotfix , < 22.1.3 July-2-2026-Hotfix (semver) Unaffected: 22.1.4 July-2-2026-Hotfix , < 22.1.4 July-2-2026-Hotfix (semver) Unaffected: 23.1.2 Aug-3-2026-Hotfix , < 23.1.2 Aug-3-2026-Hotfix (semver) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "VOS",
"vendor": "Versa",
"versions": [
{
"lessThanOrEqual": "21.2.3",
"status": "affected",
"version": "21.1.1",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.2",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.3",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.4",
"versionType": "semver"
},
{
"lessThan": "23.1.2",
"status": "affected",
"version": "23.1.2",
"versionType": "semver"
},
{
"lessThan": "22.1.2 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.2 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "22.1.3 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.3 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "22.1.4 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.4 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "23.1.2 Aug-3-2026-Hotfix",
"status": "unaffected",
"version": "23.1.2 Aug-3-2026-Hotfix",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Versa has confirmed a\u202fbuffer overflow\u202fvulnerability\u202fin the\u202fIPsec implementation\u202fon VOS, aka Versa\u202fFlexVNF. \n \n\u202fBuffer Overflow Vulnerability Description \n \nWhen a maliciously crafted IKE\u202fAuth packet is sent to VOS, the\u202fvsmd\u202fprocess crashes, thereby\u202fresulting in\u202fa Denial of Service.\u202fAn\u202fattacker\u202fcan\u202fcreate\u202fa Denial-of-Service\u202fattack on\u202fthe VOS appliances by\u202fcrafting a\u202fmalicious IKE Auth\u202fpacket and sending it to the\u202fWAN\u202finterfaces on the VOS. \n \nDuring the\u202fIKE\u202fAuthentication\u202fphase, if the IKE SA negotiation fails, and the size of the Remote ID\u202fis\u202flarger than the buffer size used to process the Remote ID,\u202fit will result in a crash of the\u202fvsmd\u202fprocess on the VOS appliance. \n \nWhat is impacted? \n \nVOS nodes configured with IPsec VPN profiles of type\u202fcontroller-staging-sdwan\u202for remote-access-server\u202fusing a WAN interface as the IPsec endpoint are vulnerable. (IPsec profiles configured with an overlay interface as the IPsec endpoint are\u202fnot\u202faffected.)\u202fThis configuration typically applies to all\u202fControllers,\u202fHub Controllers, and\u202fSSE Gateways. Additionally,\u202fsite-to-site\u202fVPN profiles configured without a peer IP address, hostname, or FQDN are also vulnerable. \n \nWhat is not impacted? \n \nThe VOS nodes listed above are not vulnerable if they are not accessible from the Internet."
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-121",
"description": "CWE-121 Stack Overflow",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T00:32:37.094Z",
"orgId": "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
"shortName": "hackerone"
},
"references": [
{
"url": "https://security-portal.versa-networks.com/emailbulletins/6a663c9aabeebad826bc8d29"
}
],
"workarounds": [
{
"lang": "en",
"value": "Disable the\u202fstaging VPN profile\u202fon Controllers and Hub Controllers when Zero-Touch Provisioning (ZTP) over the Internet is not actively\u202frequired. Enable the profile only for the duration of device bootstrapping. \n\nFor site-to-site IPsec VPN profiles without a configured remote peer, specify the remote peer IP address, hostname, or fully qualified domain name (FQDN). \n\nIf the source IP address associated with exploitation attempts is known, configure a discard or blackhole route for that IP address to block the malicious traffic."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
"assignerShortName": "hackerone",
"cveId": "CVE-2026-107245",
"datePublished": "2026-11-10T00:32:37.094Z",
"dateReserved": "2026-10-07T15:00:00.550Z",
"dateUpdated": "2026-11-10T00:32:37.094Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-107245",
"date": "2026-11-10",
"epss": "0.00183",
"percentile": "0.07924"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "VOS",
"vendor": "Versa",
"versions": [
{
"lessThanOrEqual": "21.2.3",
"status": "affected",
"version": "21.1.1",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.2",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.3",
"versionType": "semver"
},
{
"lessThan": "July 2, 2026",
"status": "affected",
"version": "22.1.4",
"versionType": "semver"
},
{
"lessThan": "23.1.2",
"status": "affected",
"version": "23.1.2",
"versionType": "semver"
},
{
"lessThan": "22.1.2 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.2 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "22.1.3 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.3 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "22.1.4 July-2-2026-Hotfix",
"status": "unaffected",
"version": "22.1.4 July-2-2026-Hotfix",
"versionType": "semver"
},
{
"lessThan": "23.1.2 Aug-3-2026-Hotfix",
"status": "unaffected",
"version": "23.1.2 Aug-3-2026-Hotfix",
"versionType": "semver"
}
]
}
],
"source": "support@hackerone.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Versa has confirmed a\u202fbuffer overflow\u202fvulnerability\u202fin the\u202fIPsec implementation\u202fon VOS, aka Versa\u202fFlexVNF. \n \n\u202fBuffer Overflow Vulnerability Description \n \nWhen a maliciously crafted IKE\u202fAuth packet is sent to VOS, the\u202fvsmd\u202fprocess crashes, thereby\u202fresulting in\u202fa Denial of Service.\u202fAn\u202fattacker\u202fcan\u202fcreate\u202fa Denial-of-Service\u202fattack on\u202fthe VOS appliances by\u202fcrafting a\u202fmalicious IKE Auth\u202fpacket and sending it to the\u202fWAN\u202finterfaces on the VOS. \n \nDuring the\u202fIKE\u202fAuthentication\u202fphase, if the IKE SA negotiation fails, and the size of the Remote ID\u202fis\u202flarger than the buffer size used to process the Remote ID,\u202fit will result in a crash of the\u202fvsmd\u202fprocess on the VOS appliance. \n \nWhat is impacted? \n \nVOS nodes configured with IPsec VPN profiles of type\u202fcontroller-staging-sdwan\u202for remote-access-server\u202fusing a WAN interface as the IPsec endpoint are vulnerable. (IPsec profiles configured with an overlay interface as the IPsec endpoint are\u202fnot\u202faffected.)\u202fThis configuration typically applies to all\u202fControllers,\u202fHub Controllers, and\u202fSSE Gateways. Additionally,\u202fsite-to-site\u202fVPN profiles configured without a peer IP address, hostname, or FQDN are also vulnerable. \n \nWhat is not impacted? \n \nThe VOS nodes listed above are not vulnerable if they are not accessible from the Internet."
}
],
"id": "CVE-2026-107245",
"lastModified": "2026-11-10T01:17:12.740",
"metrics": {},
"published": "2026-11-10T01:17:12.740",
"references": [
{
"source": "support@hackerone.com",
"url": "https://security-portal.versa-networks.com/emailbulletins/6a663c9aabeebad826bc8d29"
}
],
"sourceIdentifier": "support@hackerone.com",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-121"
}
],
"source": "support@hackerone.com",
"type": "Secondary"
}
]
}
}
}
}
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.