This content is an interview-style article featuring Patti Degnan, a cybersecurity leader whose career was influenced by her personal experience with identity theft. The article discusses her journey to becoming a CISO, leadership perspectives, and evolving cybersecurity challenges, particularly the shift from individual identity theft to broader enterprise credential threats. It highlights the growing role of CISOs as business enablers and the importance of leadership and team dynamics in cybersecurity.
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.
This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.
Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server. If Apache Iggy 0.9.0 started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, it generated a root password and wrote it to the server log file, which is enabled by default. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) let a user with only the read_servers permission download the server log files. That user could read the generated root password and log in as root.
This issue affects Apache Iggy: 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Version 0.10.0 never generates a root password, and the snapshot requires the manage_servers permission. If a 0.9.0 server generated its root password, change that password.
Dell PowerStore contains an OS Command Injection vulnerability. Exploitation could lead to arbitrary command execution with root privileges on the appliance.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0 for macOS allows an unauthenticated remote
attacker to execute arbitrary commands with the privileges of the current user
by convincing the user to open a PDF with a crafted filename and select Send.
The application embeds the attachment path in AppleScript source without
neutralizing AppleScript syntax, allowing injected do shell script expressions
to execute.
Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.
CVE-2026-84786 is a vulnerability in OpenSSL where a DANE-enabled TLS client may crash due to a NULL pointer dereference when processing a specific combination of certificate and TLSA records. This issue affects multiple OpenSSL versions prior to their respective fixed releases.
A vulnerability in OpenSSL affects the verification of maliciously crafted CMS or PKCS#7 SignedData messages when CRL checking is enabled. This flaw causes excessive CPU consumption that grows quadratically with the message size, potentially leading to denial of service conditions.
A vulnerability in OpenSSL's EVP_EncodeBlock() function can cause an integer overflow when called with an input length near INT_MAX. This overflow may lead to writing beyond the bounds of the output buffer provided by the caller, potentially causing memory corruption.
Google released Chrome version 158.0.8127.x to patch 204 security vulnerabilities, including six critical-severity bugs affecting components such as WebView, GarbageCollection, WebAudio, GPU, ANGLE, and Media. The update addresses a wide range of issues including use-after-free, authorization flaws, out-of-bounds writes/reads, and buffer overflows. No exploitation in the wild has been reported. Users are advised to update promptly to mitigate potential risks.
A vulnerability in OpenSSL's QUIC stack allows a remote attacker to queue an unlimited number of RETIRE_CONNECTION_ID frames by retransmitting NEW_CONNECTION_ID frames. This flaw affects multiple OpenSSL versions prior to their respective fixed releases.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.
Grav versions from 2.0.0 up to but not including 2.2.18 have a resource exhaustion vulnerability. Unauthenticated attackers can exploit this by sending HTTP requests with varying Host headers, causing the system to create multiple cached configurations and indexes. This can fill the disk space, leading to session, upload, and logging failures.
Grav from 2.0.0 before 2.2.18 contains a password reset poisoning vulnerability that allows anonymous attackers to redirect reset links by forging the CloudFront-Forwarded-Proto header. Attackers can send a forgot-password request with a crafted scheme value so the emailed reset link points to their host, capturing the token to take over accounts including super admins.
Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous visitors to create super-admin accounts because UserCollection::count() uses an unescaped glob() pattern. On installs whose path contains brackets or a backslash, the account count returns zero, so attackers can send requests to POST /api/v1/auth/setup or the classic admin registration form to create or overwrite administrator accounts.
Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have a vulnerability where sensitive session cookies can be cached and served to unauthorized users when lazy sessions are enabled and a shared cache is used. This can allow attackers to hijack user sessions by exploiting cached responses containing session cookies.
Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows page editors to escape the Twig sandbox by sending requests with a Host: pages header. Attackers can write configuration YAML through page folders and media .meta.yaml sidecars to register an unsandboxed Twig namespace and run shell commands as the web server user.
Grav versions from 2.0.0 up to but not including 2.2.18 have an access control bypass vulnerability. This flaw allows anonymous users to read protected pages due to shared page cache keys between admin and site scopes. The issue arises when the API plugin rebuilds the page index without enforcing frontmatter.yaml access rules, temporarily exposing members-only content until the cache is refreshed. The vulnerability is rated high severity with a CVSS 4.0 score of 8.2. A fix is available in version 2.2.18.
Grav from 2.0.0 before 2.2.18 contains an insecure blueprint trust vulnerability that allows publisher accounts to read secrets and execute PHP by planting or selecting attacker-controlled blueprint files. Attackers can abuse the import@ directive, uploaded YAML media named as the page template, or form.flash_folder to leak password hashes and keys or invoke static PHP methods for code execution.