CVE-2015-8096
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to...
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
Exploit likelihood
What each source reports
NVD Score used
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
- Record
CVE-2015-8096- CVSS 2.0
- 10.0 High
AV:N/AC:L/Au:N/C:C/I:C/A:C - Weakness
- CWE-119, CWE-189
- Updated
- 2026-11-02
CVE List No score
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
- Record
CVE-2015-8096- Updated
- 2026-11-02
EUVDEUVD-2015-7989 No score
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
- Record
EUVD-2015-7989- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-hcvg-vqp3-m7mq No score
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to...
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
- Record
GHSA-hcvg-vqp3-m7mq- Weakness
- CWE-119
- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2015-8096 is a high vulnerability (CVSS 10.0) in Google Picasa, published November 9, 2015. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 4.02%, the 90th percentile. No source names a fixed version.