Skip to main content

Threats Tagged 'cve-2026-15043'

View all threats tagged with 'cve-2026-15043'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-15043

Threats Tagged 'cve-2026-15043'

Click on any threat for detailed analysis and mitigation recommendations

0

This security update for perl-DBI addresses multiple vulnerabilities including unauthorized file access due to symbolic link validation failure, bypass of file-backed filters from incorrect predicate evaluation, a memory-amplification denial of service via unbounded path index in profile parsing, and a process crash caused by out-of-bounds access in statement handle processing. The vulnerabilities collectively pose a high severity risk. The update targets specific SUSE platform versions and architectures.

Join the discussion

DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text. DBI::SQL::Nano, DBI's built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, <= was evaluated using Perl's ge operator, and >= was evaluated using Perl's le operator. SQL::Nano is the fallback query engine for DBI's file-backed drivers (DBD::File, DBD::DBM, CSV-style drivers) whenever SQL::Statement is not installed, and is forced whenever DBI_SQL_NANO=1. Queries over such tables use these predicates directly. The impact depends on the context. Where an application relies on a WHERE clause to filter file-backed data for policy or authorization, an inverted <=/>= comparison silently returns the wrong rows.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-15043
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses