Ivanti endpoint manager, absolute path traversal: 4 records, one defect family
Ivanti endpoint manager has been reported 4 separate times for the same kind of mistake, CWE-36, all published on 2025-01-14. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.
What this page is, and what it is not
The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Ivanti endpoint manager and carries CWE-36, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.
That is 4 filings, all published on 2025-01-14, landing on the same weakness class in the same product. At this count it is a repeat rather than a pattern, and the roster below is short enough to read in full. This is what we held on 2026-09-20.
A repeat is evidence about where to look. If you are reviewing Ivanti endpoint manager, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.
What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.
The names the authorities used
One spelling, used by every authority that filed one of these records: ivanti endpoint manager.
Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.
What the records offer
All 4 records publish a fixed version.
3 records are listed by CISA with a required action, which carries a federal remediation deadline on its own page.
What this family was researched, not held
Four Ivanti EPM path flaws in one hash calculating class
All four records are absolute path traversal in Ivanti Endpoint Manager, and the researchers who reported them place them in a single component. Horizon3.ai found them in WSVulnerabilityCore.dll, in four hash calculation methods that take a path from the request: GetHashForFile, GetHashForSingleFile, GetHashForWildcard and GetHashForWildcardRecursive. Each builds a path from user supplied input without sanitising it, so an unauthenticated caller can point the server at a remote UNC path and coerce it into authenticating to a machine the attacker controls, which the researchers then relayed to LDAP. Horizon3 reported them on 15 October 2024, Ivanti patched on 13 January 2025, and the researchers published details and a proof of concept on 19 February 2025 after agreeing to hold them for thirty days. Ivanti said it was not aware of exploitation before public disclosure, and CISA added three of the four to its exploited catalog on 10 March 2025.
No known exploitation at disclosure was not a reason to defer here, because the catalog listing arrived in March for three of the four. The vendor fixed all four in its January 2025 update, which is a fact about that release rather than about this grouping.
This note does not establish that these records share a vulnerability, an install, or a fix. The grouping says only that the records read alike, one product and one weakness class, and closing one of them is not evidence about the rest.
Written from horizon3.ai, cybersecuritydive.com, cisa.gov. Stated at high confidence. Nothing in this box is a value the index holds, and none of it opens a receipt.
What tells these apart
Nothing held does. Every record here carries the same title, or none, the same weakness class, and the same publication day, and the index holds no distinguishing value for any of them. The rows below are listed by identifier for that reason. That is the state of the sources, not a gap in this page.
What this page does not cover
This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Everything this vendor has, including records outside this family:
4 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.