CVE-2007-1265
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKMail 1.9.5 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents KMail from visually distinguishing between signed and unsigned portions of OpenPGP messages with multiple components, which allows remote attackers to forge the contents of a message without detection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKMail 1.9.5 and earlier fails to properly handle the --status-fd argument when invoking GnuPG, causing the application to be unable to parse and distinguish which parts of multipart OpenPGP messages are actually signed versus unsigned. This allows an attacker to craft a message with mixed signed/unsigned components where unsigned portions can be modified without triggering any visual warning to the recipient.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.0.29.2= 1.0.23= 1.0.24= 1.0.25= 1.0.26= 1.0.27= 1.0.28= 1.0.29= 1.0.29.1= 1.0.29.2= 1.1= 1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:C/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify KMail installationCheck for KMail installation and retrieve version - on Debian-based systems: dpkg -l | grep -i kmail; on RPM-based systems: rpm -qa | grep -i kmail; or check KHelpCenter: about kde; alternatively look for kmail in /usr/bin or /usr/local/binAffected if KMail is installed with version 1.9.5 or earlier (including 0.0.29.2, 1.0.x series through 1.0.29.2, 1.1, or 1.2)
-
Confirm exact KMail versionRun kmail --version or kmail -v to display the precise version number installedAffected if Version output matches any of: 0.0.29.2, 1.0.23, 1.0.24, 1.0.25, 1.0.26, 1.0.27, 1.0.28, 1.0.29, 1.0.29.1, 1.0.29.2, 1.1, 1.2, or any 1.9.x version up to and including 1.9.5
-
Verify GnuPG integration statusOpen KMail, go to Settings > Configure KMail > Plugins or Security, and check if the GnuPG plugin or OpenPGP support is enabledAffected if GnuPG/OpenPGP encryption and signing support is enabled in KMail
-
Check for multipart signed message handlingSend or receive a multipart OpenPGP signed message and observe whether all components are properly verified - unsigned portions may be modified without visual warningAffected if The installed version fails to properly parse --status-fd output from GnuPG, causing inability to distinguish signed from unsigned parts in multipart messages
User is affected if KMail version is 1.9.5 or earlier (including listed 1.0.x and 1.x versions) AND GnuPG/OpenPGP signing is enabled, allowing unsigned portions of multipart signed messages to be modified without warning.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to KMail version 1.9.6 or later which properly implements GnuPG --status-fd handling to correctly parse and verify all signed components in multipart messages.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-1265 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data