CVE-2026-92002: MISP: Authentication failure logging suppressed during Redis unavailability

Published Sep 15, 2026
·
Updated

Affected versions of MISP use Redis to throttle repeated authentication-failure log entries. The intent is to avoid excessive duplicate logs while still recording failed authentication activity.

However, User->setupRedis() returns false when Redis cannot be reached. The vulnerable shouldLog() logic only returned true when a Redis instance existed and no throttle key was present. Therefore, when Redis was unavailable, the function did not allow the log write at all, effectively silencing authentication-failure logging for the duration of the outage.

Version affected: ≤2.5.45

Affected Software

1 affected component
MISP<=2.5.45

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MISP to a version that resolves this vulnerability.

    Fixed in ≤2.5.45Patch MISP: Authentication failure logging suppressed during Redis unavailability
  2. Configuration

    Ensure MISP uses the updated _shouldLog() logic that explicitly checks whether the Redis connection is available before attempting to use it, so that when Redis is unavailable the system becomes fail-open for security logging (logs failed authentication events instead of silencing them).

    MISP (Redis throttling for authentication-failure logging) Redis connection availability check in _shouldLog() = enabled

Event History

Sep 15, 2026
CVE Published
via MITRE·11:24 AM
Data Sourced
via MITRE·11:24 AM
RemedyDescriptionWeakness

Frequently Asked Questions

1

When does the logging gap occur?

It occurs when MISP cannot reach Redis. During that Redis outage, failed authentication attempts are not written to the authentication-failure log.

2

What deployments are affected?

MISP versions 2.5.45 and earlier are affected. The issue depends on Redis becoming unavailable, because Redis is used to control repeated authentication-failure log entries.

3

How can administrators determine whether they may have missed authentication failures?

Review periods when the MISP instance could not reach Redis. Authentication failures occurring during those periods may have generated no authentication-failure log entries.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203