How severe is CVE-2006-7216?

CVE-2006-7216 has a CVSS 2.0 base score of 4.0, rated medium severity.

Is CVE-2006-7216 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-7216?

CVE-2006-7216 primarily affects Apache Derby. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-7216?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2006-7216 published?

CVE-2006-7216 was published on 2007-07-05 and last updated on 2026-06-16.

CVE-2006-7216

CVE-2006-7216 is a medium-severity vulnerability in Apache Derby with a CVSS 2.0 base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.0)
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Apache Derby
Published: 2007-07-05
Last modified: 2026-06-16

Description

Apache Derby before 10.2.1.6 does not determine privilege requirements for lock table statements at compilation time, and consequently does not enforce privilege requirements at execution time, which allows remote authenticated users to lock arbitrary tables.

Frequently asked questions

What is CVE-2006-7216?: Apache Derby before 10.2.1.6 does not determine privilege requirements for lock table statements at compilation time, and consequently does not enforce privilege requirements at execution time, which allows remote authenticated users to lock arbitrary tables.
How severe is CVE-2006-7216?: CVE-2006-7216 has a CVSS 2.0 base score of 4.0, rated medium severity.
Is CVE-2006-7216 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-7216?: CVE-2006-7216 primarily affects Apache Derby. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-7216?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2006-7216 published?: CVE-2006-7216 was published on 2007-07-05 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:apache:derby:10.1.1.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:derby:10.1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:apache:derby:10.1.3.1:*:*:*:*:*:*:*

More vulnerabilities in Apache Derby

CVE-2022-46337 — Critical (CVSS 9.8): A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this…
CVE-2015-1832 — Critical (CVSS 9.1): XML external entity (XXE) vulnerability in the SqlXmlUtil code in Apache Derby before 10.12.1.1, when a Java Security…
CVE-2010-2232 — High (CVSS 7.5): In Apache Derby 10.1.2.1, 10.2.2.0, 10.3.1.4, and 10.4.1.3, Export processing may allow an attacker to overwrite an…
CVE-2018-1313 — Medium (CVSS 5.3): In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network…
CVE-2005-4849 — Medium (CVSS 5.0): Apache Derby before 10.1.2.1 exposes the (1) user and (2) password attributes in cleartext via (a) the RDBNAM parameter…
CVE-2006-7217 — Medium (CVSS 4.0): Apache Derby before 10.2.1.6 does not determine schema privilege requirements during the DropSchemaNode bind phase,…

All CVEs affecting Apache Derby →