PULSE
FEED
ransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***upransomsarcoma reclama a Ivan Smith Furniture · PH · Retail & E-Commerceransomwhitearmor reclama a Gamdom V2 · Otherransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***upransomsarcoma reclama a Ivan Smith Furniture · PH · Retail & E-Commerceransomwhitearmor reclama a Gamdom V2 · Other
← Todos los CVEs
CVE Watch26 oct 2026

CVE-2026-32803

Dell PowerScale OneFS versions 9.5.0.0 through 9.5.1.6, 9.6.0.0 through 9.7.1.13, 9.8.0.0 through 9.10.1.5 and 9.11.0.0 through 9.12.0.1 con

CVSS

3.3

Bajo

EPSS

0.1%

p0

KEV

—

Exploit Today

0

0-100

Publicado: 8 may 2026 · Última mod.: 26 oct 2026 · CWE-778

EPSS · 30d
0.1%EPSS · 30 días0.1%
2026-10-032026-10-30
Descripción técnica

Dell PowerScale OneFS versions 9.5.0.0 through 9.5.1.6, 9.6.0.0 through 9.7.1.13, 9.8.0.0 through 9.10.1.5 and 9.11.0.0 through 9.12.0.1 contains an Insufficient Logging vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information tampering.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1083112.7 BAJ
15.3%
——5Tanium addressed an insufficient logging vulnerability in Tanium Server.4d
CVE-2026-1153572.2 BAJ
11.2%
——3OpenBao before 2.6.4 and 2.7.x before 2.7.1 fails to write response audit entries for the unauthenticated sys/generate-root, sys/rekey, and sys/rekey-recovery-key endpoints when request audit logging succeeds but response audit logging fails. An attacker using these endpoints can complete root token generation or rekey operations without a corresponding response audit record, hindering forensic detection.9d
CVE-2026-859597.5 ALT
33.9%
——10Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not consistently record successful authentication events in audit logs, which could limit customers' ability to detect and investigate unauthorized access or credential misuse.16d
CVE-2026-1052435.3 MED
56.8%
——17Insufficient Logging vulnerability in the EventLogAppender of Apache log4net. Long messages were truncated to a fixed size that exceeds what the Windows Event Log accepts once the log and source names are counted, and the event log then stored nothing and reported nothing. A party whose data reaches a log message could suppress the whole record by making it long enough. Only applications on Windows that use EventLogAppender are affected. This issue affects Apache log4net: from 1.2.9 before 3.5.0. Users are recommended to upgrade to version 3.5.0, which fixes the issue.23d
CVE-2026-181614.3 MED
28.1%
——8IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote authenticated attacker to falsify transaction audit logs due to improper validation of a client-supplied HTTP header.25d
CVE-2026-92002—
45.0%
——14Affected 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.4546d