UBUNTU-CVE-2026-78030 (CVE-2026-78030)
Vulnerability from osv_ubuntu – Published: 2026-09-19 11:16 – Updated: 2026-09-29 08:39 – Source websiteDBI versions before 1.653 for Perl load arbitrary modules via unvalidated dbm_type and dbm_mldbm attributes in DBD::DBM. DBD::DBM passes the dbm_type and dbm_mldbm connect attributes to require without checking that the value names a module. require treats a path-shaped string as a literal filename and does not consult @INC, so the attribute chooses the file that Perl loads and runs. The MLDBM::Serializer:: prefix that DBD::DBM prepends to dbm_mldbm is not a boundary: only the :: separators are rewritten to /, so a value containing / traverses out of the serializer directory. The value is also assigned to $MLDBM::Serializer, which MLDBM requires the same way when it ties the table. A caller that lets an untrusted party influence either attribute, for example through a DSN fragment or a parameter that selects a storage backend, runs the file-scope code of whatever module the value names. For example, my $dsn = "dbi:DBM:f_dir=/var/db;dbm_type=../../Untrusted.pm" my $dbh = DBI->connect( $dsn ); Note that DBD::Gofer forwards connect attributes to the server side, and DBI::ProxyServer checks only that a DSN starts with a driver prefix.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.630-1ubuntu0.1~esm8"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.630-1ubuntu0.1~esm8?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.627-1",
"1.628-1",
"1.630-1",
"1.630-1ubuntu0.1~esm1",
"1.630-1ubuntu0.1~esm4",
"1.630-1ubuntu0.1~esm5",
"1.630-1ubuntu0.1~esm6",
"1.630-1ubuntu0.1~esm8"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.634-1ubuntu0.2+esm4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.634-1ubuntu0.2+esm4?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.633-1",
"1.634-1",
"1.634-1build1",
"1.634-1ubuntu0.1",
"1.634-1ubuntu0.2",
"1.634-1ubuntu0.2+esm1",
"1.634-1ubuntu0.2+esm2",
"1.634-1ubuntu0.2+esm4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.640-1ubuntu0.3+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.640-1ubuntu0.3+esm3?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.637-1",
"1.639-1",
"1.640-1",
"1.640-1ubuntu0.1",
"1.640-1ubuntu0.2",
"1.640-1ubuntu0.3",
"1.640-1ubuntu0.3+esm1",
"1.640-1ubuntu0.3+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.643-1ubuntu0.1+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.643-1ubuntu0.1+esm3?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.642-1",
"1.642-1build1",
"1.643-1",
"1.643-1ubuntu0.1",
"1.643-1ubuntu0.1+esm1",
"1.643-1ubuntu0.1+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.643-3ubuntu0.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.643-3ubuntu0.3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.643-3build2",
"1.643-3build3",
"1.643-3ubuntu0.1",
"1.643-3ubuntu0.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.643-4ubuntu0.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.643-4ubuntu0.3?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.643-4",
"1.643-4build1",
"1.643-4build2",
"1.643-4build3",
"1.643-4ubuntu0.1",
"1.643-4ubuntu0.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libdbi-perl",
"binary_version": "1.647-1ubuntu0.26.04.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "libdbi-perl",
"purl": "pkg:deb/ubuntu/libdbi-perl@1.647-1ubuntu0.26.04.3?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.647-1",
"1.647-1build1",
"1.647-1ubuntu0.26.04.1",
"1.647-1ubuntu0.26.04.3"
]
}
],
"aliases": [],
"details": "DBI versions before 1.653 for Perl load arbitrary modules via unvalidated dbm_type and dbm_mldbm attributes in DBD::DBM. DBD::DBM passes the dbm_type and dbm_mldbm connect attributes to require without checking that the value names a module. require treats a path-shaped string as a literal filename and does not consult @INC, so the attribute chooses the file that Perl loads and runs. The MLDBM::Serializer:: prefix that DBD::DBM prepends to dbm_mldbm is not a boundary: only the :: separators are rewritten to /, so a value containing / traverses out of the serializer directory. The value is also assigned to $MLDBM::Serializer, which MLDBM requires the same way when it ties the table. A caller that lets an untrusted party influence either attribute, for example through a DSN fragment or a parameter that selects a storage backend, runs the file-scope code of whatever module the value names. For example, my $dsn = \"dbi:DBM:f_dir=/var/db;dbm_type=../../Untrusted.pm\" my $dbh = DBI-\u003econnect( $dsn ); Note that DBD::Gofer forwards connect attributes to the server side, and DBI::ProxyServer checks only that a DSN starts with a driver prefix.",
"id": "UBUNTU-CVE-2026-78030",
"modified": "2026-09-29T08:39:22Z",
"published": "2026-09-19T11:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-78030"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78030"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-78030"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.