Authentication Bypass
Affects Log360 and EventLog Analyzer builds 13070 and earlier, where local collector registration is exposed to unauthenticated requests. Fixed in build 13071.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 13071
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 13071.
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 1.54% · 74th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 13071
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
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.
Read the original 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
Upgrade to a fixed version: 13071.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Zohocorp Log360
fixed in 13071
- Zohocorp EventLog Analyzer
fixed in 13071
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-16900
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: cve.now feed data
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: manageengine.com
Which versions are affected by CVE-2026-16900?
Log360: before 13071. EventLog Analyzer: before 13071.Source: cve.now feed data
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: manageengine.com
How do I fix CVE-2026-16900?
Upgrade to build 13071 or later, which is the fixed build listed for both products.Source: manageengine.com