JVNDB-2026-040671
Vulnerability from jvndb - Published: 2026-10-30 10:57 - Updated:2026-10-30 10:57
Severity
Summary
Multiple Vulnerabilities in JP1/IT Desktop Management 2 - Smart Device Manager
Details
Multiple vulnerabilities have been found in JP1/IT Desktop Management 2 - Smart Device Manager.
References
Impacted products
| Vendor | Product | |
|---|---|---|
{
"@rdf:about": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-040671.html",
"dc:date": "2026-10-30T19:57+09:00",
"dcterms:issued": "2026-10-30T19:57+09:00",
"dcterms:modified": "2026-10-30T19:57+09:00",
"description": "Multiple vulnerabilities have been found in JP1/IT Desktop Management 2 - Smart Device Manager.",
"link": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-040671.html",
"sec:cpe": {
"#text": "cpe:/a:hitachi:jp1%2fit_desktop_management_2-smart_device_manager",
"@product": "JP1/IT Desktop Management 2 - Smart Device Manager",
"@vendor": "Hitachi, Ltd",
"@version": "2.2"
},
"sec:cvss": {
"@score": "7.5",
"@severity": "High",
"@type": "Base",
"@vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"@version": "3.0"
},
"sec:identifier": "JVNDB-2026-040671",
"sec:references": [
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-21290",
"@id": "CVE-2021-21290",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-21409",
"@id": "CVE-2021-21409",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-37136",
"@id": "CVE-2021-37136",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-37137",
"@id": "CVE-2021-37137",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2021-43797",
"@id": "CVE-2021-43797",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2022-24823",
"@id": "CVE-2022-24823",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2022-41881",
"@id": "CVE-2022-41881",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2023-34462",
"@id": "CVE-2023-34462",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2024-29025",
"@id": "CVE-2024-29025",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2024-47535",
"@id": "CVE-2024-47535",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2025-25193",
"@id": "CVE-2025-25193",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2025-55163",
"@id": "CVE-2025-55163",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2025-58056",
"@id": "CVE-2025-58056",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2025-58057",
"@id": "CVE-2025-58057",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2025-67735",
"@id": "CVE-2025-67735",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-33870",
"@id": "CVE-2026-33870",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-33871",
"@id": "CVE-2026-33871",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-41417",
"@id": "CVE-2026-41417",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42578",
"@id": "CVE-2026-42578",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42579",
"@id": "CVE-2026-42579",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42580",
"@id": "CVE-2026-42580",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42581",
"@id": "CVE-2026-42581",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42582",
"@id": "CVE-2026-42582",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42583",
"@id": "CVE-2026-42583",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42584",
"@id": "CVE-2026-42584",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42585",
"@id": "CVE-2026-42585",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42586",
"@id": "CVE-2026-42586",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-42587",
"@id": "CVE-2026-42587",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44248",
"@id": "CVE-2026-44248",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44249",
"@id": "CVE-2026-44249",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44250",
"@id": "CVE-2026-44250",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44890",
"@id": "CVE-2026-44890",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44891",
"@id": "CVE-2026-44891",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-44893",
"@id": "CVE-2026-44893",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-45416",
"@id": "CVE-2026-45416",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-45536",
"@id": "CVE-2026-45536",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-45673",
"@id": "CVE-2026-45673",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-45674",
"@id": "CVE-2026-45674",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-46340",
"@id": "CVE-2026-46340",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-47244",
"@id": "CVE-2026-47244",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-47691",
"@id": "CVE-2026-47691",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-48006",
"@id": "CVE-2026-48006",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-48043",
"@id": "CVE-2026-48043",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-48059",
"@id": "CVE-2026-48059",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-50010",
"@id": "CVE-2026-50010",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-50011",
"@id": "CVE-2026-50011",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-50020",
"@id": "CVE-2026-50020",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-50560",
"@id": "CVE-2026-50560",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-55831",
"@id": "CVE-2026-55831",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-55833",
"@id": "CVE-2026-55833",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-55851",
"@id": "CVE-2026-55851",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56745",
"@id": "CVE-2026-56745",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56746",
"@id": "CVE-2026-56746",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56817",
"@id": "CVE-2026-56817",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56819",
"@id": "CVE-2026-56819",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56820",
"@id": "CVE-2026-56820",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56821",
"@id": "CVE-2026-56821",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-56822",
"@id": "CVE-2026-56822",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59898",
"@id": "CVE-2026-59898",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59899",
"@id": "CVE-2026-59899",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59900",
"@id": "CVE-2026-59900",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59901",
"@id": "CVE-2026-59901",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59919",
"@id": "CVE-2026-59919",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59920",
"@id": "CVE-2026-59920",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-59921",
"@id": "CVE-2026-59921",
"@source": "CVE"
},
{
"#text": "https://www.cve.org/CVERecord?id=CVE-2026-62380",
"@id": "CVE-2026-62380",
"@source": "CVE"
}
],
"title": "Multiple Vulnerabilities in JP1/IT Desktop Management 2 - Smart Device Manager"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…