MISP 的受影响版本会在请求以异常终止时记录错误的访问日志数据。 原因是 继承自 ,导致异常渲染时再次执行应用启动路径。结果, 会对同一个 HTTP 请求调用两次 。第二个延迟写入器测量的是错误控制器的执行时间,而非原始请求,可能会覆盖第一次写入创建的数据行。受影响的字段包括:请求持续时间、SQL 查询次数、内存使用量,以及可能包含记录的查询日志。 该 bug 之前未被明显暴露,是因为同一个模型实例保留了首次保存行的 ID,导致后续的保存操作执行的是 UPDATE(更新)而非插入一条明显的重复行。 受影响版本:≤
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-91825 | 7.1 HIGH | MISP: Missing Authorization Check for Event Sharing Group When Distribution Field Is Omitt |
| CVE-2026-91846 | 7.1 HIGH | MISP Collection Element Add Missing Authorization on Referenced Object UUID |
| CVE-2026-91819 | 6.9 MEDIUM | MISP: HTTP Method Override Bypasses CSRF and Form Validation in BetterSecurityComponent |
| CVE-2026-92003 | 6.9 MEDIUM | MISP Unthrottled Authentication Failure Log Writes Enable Resource Exhaustion |
| CVE-2026-91851 | 5.3 MEDIUM | MISP Dashboard Template ACL Bypass Due to VARCHAR-to-Integer Type Coercion in Permission F |
| CVE-2026-91857 | 5.3 MEDIUM | MISP: State-changing actions accessible via GET request enabling CSRF |
| CVE-2026-92002 | 5.1 MEDIUM | MISP: Authentication failure logging suppressed during Redis unavailability |
No comments yet