本ページは otfcc_project otfcc に影響する公開済み CVE（NVD の CPE 経由で関連付け）を列挙します。各行に深刻度指標・概要・公開日が含まれます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2022-35059 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6c0414. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35058 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b05ce. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35056 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b0478. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35055 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6c0473. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35054 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6171b2. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35053 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x61731f. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35052 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b84b1. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35051 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b55af. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35050 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b04de. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35049 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b03b5. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35048 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b0b2c. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35047 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b05aa. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35046 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b0466. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35045 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b0d63. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35044 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x617087. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35043 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6c08a6. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35042 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x4adb11. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35041 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b558f. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35040 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b5567. | [email protected] | 6.5 | 0.72% | 2022-10-14 | 2026-06-17 |
| CVE-2022-35039 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e20a0. | [email protected] | 6.5 | 0.75% | 2022-09-22 | 2026-06-17 |