i believe that this is actually an issue with webkit itself, not the libqt4-webkit package (which uses webkit as a library). CVE-2008-1025 seems to indicate that the issue is wholely within webkit (there is no mention of qt). submitter, do you have further details that would confirm that the problem also resides in libqt4-webkit? otherwise, this bug should be reassigned to webkit.