@blamejs/exceptd-skills 0.18.17 → 0.18.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -54,9 +54,11 @@
54
54
  "CVE-2025-20393",
55
55
  "CVE-2025-54236",
56
56
  "CVE-2025-6558",
57
+ "CVE-2026-12569",
57
58
  "CVE-2026-21858",
58
59
  "CVE-2026-32201",
59
60
  "CVE-2026-34197",
61
+ "CVE-2026-34910",
60
62
  "CVE-2026-6973"
61
63
  ],
62
64
  "framework_controls_partially_addressing": [
@@ -113,13 +115,16 @@
113
115
  "CVE-2024-7399",
114
116
  "CVE-2025-2749",
115
117
  "CVE-2025-27920",
118
+ "CVE-2025-34028",
116
119
  "CVE-2025-4632",
117
120
  "CVE-2025-51480",
118
121
  "CVE-2025-6218",
119
122
  "CVE-2025-67818",
120
123
  "CVE-2025-8110",
124
+ "CVE-2026-20262",
121
125
  "CVE-2026-22218",
122
126
  "CVE-2026-25592",
127
+ "CVE-2026-34909",
123
128
  "CVE-2026-34926"
124
129
  ],
125
130
  "framework_controls_partially_addressing": [
@@ -211,6 +216,7 @@
211
216
  "evidence_cves": [
212
217
  "CVE-2014-6278",
213
218
  "CVE-2023-39780",
219
+ "CVE-2023-44221",
214
220
  "CVE-2023-6019",
215
221
  "CVE-2024-11120",
216
222
  "CVE-2024-12987",
@@ -218,6 +224,7 @@
218
224
  "CVE-2025-11953",
219
225
  "CVE-2025-12686",
220
226
  "CVE-2025-1753",
227
+ "CVE-2025-1976",
221
228
  "CVE-2025-48703",
222
229
  "CVE-2025-54136",
223
230
  "CVE-2025-54948",
@@ -238,6 +245,7 @@
238
245
  "CVE-2026-30623",
239
246
  "CVE-2026-30624",
240
247
  "CVE-2026-30625",
248
+ "CVE-2026-34910",
241
249
  "CVE-2026-39987",
242
250
  "CVE-2026-40933",
243
251
  "CVE-2026-42271"
@@ -411,6 +419,7 @@
411
419
  "CVE-2024-56145",
412
420
  "CVE-2025-11837",
413
421
  "CVE-2025-1550",
422
+ "CVE-2025-1976",
414
423
  "CVE-2025-32432",
415
424
  "CVE-2025-3248",
416
425
  "CVE-2025-33236",
@@ -425,6 +434,7 @@
425
434
  "CVE-2025-61882",
426
435
  "CVE-2025-6204",
427
436
  "CVE-2025-62848",
437
+ "CVE-2025-67038",
428
438
  "CVE-2025-8875",
429
439
  "CVE-2025-8876",
430
440
  "CVE-2026-0766",
@@ -690,7 +700,9 @@
690
700
  "CVE-2025-31125",
691
701
  "CVE-2025-33073",
692
702
  "CVE-2025-59230",
693
- "CVE-2026-35616"
703
+ "CVE-2026-34908",
704
+ "CVE-2026-35616",
705
+ "CVE-2026-48907"
694
706
  ],
695
707
  "framework_controls_partially_addressing": [
696
708
  "NIST-800-53-AC-3",
@@ -787,10 +799,12 @@
787
799
  "CVE-2020-24363",
788
800
  "CVE-2025-32433",
789
801
  "CVE-2025-3248",
802
+ "CVE-2025-34028",
790
803
  "CVE-2025-4008",
791
804
  "CVE-2025-49596",
792
805
  "CVE-2025-61757",
793
806
  "CVE-2026-0300",
807
+ "CVE-2026-20253",
794
808
  "CVE-2026-24423",
795
809
  "CVE-2026-26190",
796
810
  "CVE-2026-33017",
@@ -1312,6 +1326,7 @@
1312
1326
  "CVE-2024-7694",
1313
1327
  "CVE-2025-2749",
1314
1328
  "CVE-2025-31324",
1329
+ "CVE-2025-3928",
1315
1330
  "CVE-2025-52691",
1316
1331
  "CVE-2026-21877"
1317
1332
  ],
@@ -1410,6 +1425,7 @@
1410
1425
  "CVE-2025-68664",
1411
1426
  "CVE-2025-68665",
1412
1427
  "CVE-2025-8747",
1428
+ "CVE-2026-12569",
1413
1429
  "CVE-2026-20131",
1414
1430
  "CVE-2026-20963",
1415
1431
  "CVE-2026-3059",
@@ -1954,6 +1970,7 @@
1954
1970
  "CVE-2025-25297",
1955
1971
  "CVE-2025-56520",
1956
1972
  "CVE-2025-61884",
1973
+ "CVE-2026-20230",
1957
1974
  "CVE-2026-22219"
1958
1975
  ],
1959
1976
  "framework_controls_partially_addressing": [
@@ -2384,6 +2401,7 @@
2384
2401
  "CVE-2008-4250",
2385
2402
  "CVE-2014-3931",
2386
2403
  "CVE-2025-14174",
2404
+ "CVE-2025-31200",
2387
2405
  "CVE-2025-31277",
2388
2406
  "CVE-2025-6543",
2389
2407
  "CVE-2025-6965",
@@ -2433,6 +2451,7 @@
2433
2451
  "CVE-2025-0282",
2434
2452
  "CVE-2025-20352",
2435
2453
  "CVE-2025-22457",
2454
+ "CVE-2025-42599",
2436
2455
  "CVE-2025-53521"
2437
2456
  ],
2438
2457
  "last_verified": "2026-05-18",
@@ -2869,6 +2888,7 @@
2869
2888
  ],
2870
2889
  "related_weaknesses": [],
2871
2890
  "evidence_cves": [
2891
+ "CVE-2025-24054",
2872
2892
  "CVE-2025-33053"
2873
2893
  ],
2874
2894
  "last_verified": "2026-05-18",
@@ -4669,6 +4689,7 @@
4669
4689
  ],
4670
4690
  "skills_referencing": [],
4671
4691
  "evidence_cves": [
4692
+ "CVE-2024-38475",
4672
4693
  "CVE-2026-20245"
4673
4694
  ],
4674
4695
  "framework_controls_partially_addressing": [],
@@ -4739,5 +4760,88 @@
4739
4760
  "real_requirement": "Complete, deny-by-default comparison logic that enumerates every distinguishing factor for a security decision; security filters must fail closed on any unmatched factor rather than forwarding the default case.",
4740
4761
  "lag_notes": "Frameworks specify that filtering exist (SC-7 boundary protection) but not that comparison logic be complete and fail-closed across all factors. Partial-match forwarding passes a control review while leaving an access-control bypass.",
4741
4762
  "last_verified": "2026-06-13"
4763
+ },
4764
+ "CWE-1220": {
4765
+ "id": "CWE-1220",
4766
+ "name": "Insufficient Granularity of Access Control",
4767
+ "abstraction": "Base",
4768
+ "category": "Access Control",
4769
+ "description": "The product implements access controls via a policy or other feature with the intention to disable or restrict accesses, but the access-control granularity is too coarse, so a protected resource can be reached at a finer level than the policy distinguishes. Cited by NVD for the Apple RPAC pointer-authentication bypass (CVE-2025-31201), where the protection's granularity was insufficient to stop an arbitrary read/write primitive.",
4770
+ "top_25_rank_2024": null,
4771
+ "top_25_rank_2025": null,
4772
+ "view_memberships": [
4773
+ "CWE-1000"
4774
+ ],
4775
+ "related_attack_patterns_capec": [
4776
+ "CAPEC-1",
4777
+ "CAPEC-180"
4778
+ ],
4779
+ "skills_referencing": [],
4780
+ "evidence_cves": [
4781
+ "CVE-2025-31201"
4782
+ ],
4783
+ "framework_controls_partially_addressing": [
4784
+ "NIST-800-53-AC-3",
4785
+ "ISO-27001-2022-A.5.15",
4786
+ "NIST-800-53-AC-6"
4787
+ ],
4788
+ "real_requirement": "Access-control boundaries enforced at the granularity of the protected resource, not a coarser policy unit; hardware/firmware protection mechanisms (e.g. pointer authentication) must cover every reachable primitive, not a representative subset.",
4789
+ "lag_notes": "AC-3 attests that an authorization framework exists; CWE-1220 is specifically about the framework's resolution being too coarse to stop the exploited path — compliance does not measure granularity.",
4790
+ "last_verified": "2026-06-26"
4791
+ },
4792
+ "CWE-61": {
4793
+ "id": "CWE-61",
4794
+ "name": "UNIX Symbolic Link (Symlink) Following",
4795
+ "abstraction": "Variant",
4796
+ "category": "Path Resolution",
4797
+ "description": "The product, when opening a file or directory, does not sufficiently account for the file being a symbolic link that resolves to a target outside of the intended control sphere, so an attacker who controls the link can cause the product to read or write a file it should not. A child of CWE-59 (improper link resolution). Cited by NVD for the LiteSpeed cPanel plugin symlink-following flaw (CVE-2026-54420).",
4798
+ "top_25_rank_2024": null,
4799
+ "top_25_rank_2025": null,
4800
+ "view_memberships": [
4801
+ "CWE-1000"
4802
+ ],
4803
+ "related_attack_patterns_capec": [
4804
+ "CAPEC-27",
4805
+ "CAPEC-76"
4806
+ ],
4807
+ "skills_referencing": [],
4808
+ "evidence_cves": [
4809
+ "CVE-2026-54420"
4810
+ ],
4811
+ "framework_controls_partially_addressing": [
4812
+ "NIST-800-53-AC-6",
4813
+ "ISO-27001-2022-A.8.3"
4814
+ ],
4815
+ "real_requirement": "Resolve and validate the final target of any link before opening it; on shared-tenant hosts, refuse to follow links that cross account/control-sphere boundaries (O_NOFOLLOW, post-resolution path checks, per-tenant chroot).",
4816
+ "lag_notes": "File-permission controls assume the path names the intended object; a symlink defeats that assumption at resolution time, which a permissions audit does not exercise.",
4817
+ "last_verified": "2026-06-26"
4818
+ },
4819
+ "CWE-424": {
4820
+ "id": "CWE-424",
4821
+ "name": "Improper Protection of Alternate Path",
4822
+ "abstraction": "Class",
4823
+ "category": "Access Control",
4824
+ "description": "The product does not sufficiently protect all of the possible paths that a user can take to access restricted functionality or a resource, so an alternate route reaches what the primary route guards. A protection-mechanism failure (related to CWE-693). Cited by NVD for the Yii framework alternate-path bypass that leads to remote code execution (CVE-2024-58136).",
4825
+ "top_25_rank_2024": null,
4826
+ "top_25_rank_2025": null,
4827
+ "view_memberships": [
4828
+ "CWE-1000"
4829
+ ],
4830
+ "related_attack_patterns_capec": [
4831
+ "CAPEC-127",
4832
+ "CAPEC-19"
4833
+ ],
4834
+ "skills_referencing": [],
4835
+ "evidence_cves": [
4836
+ "CVE-2024-58136"
4837
+ ],
4838
+ "framework_controls_partially_addressing": [
4839
+ "NIST-800-53-AC-3",
4840
+ "NIST-800-53-SC-7",
4841
+ "ISO-27001-2022-A.8.8"
4842
+ ],
4843
+ "real_requirement": "Enumerate and apply the same authorization and input-validation checks to every code path that reaches a protected resource, including framework-internal alternate routes; deny-by-default for any path not explicitly modeled.",
4844
+ "lag_notes": "An access-control audit typically tests the documented path; CWE-424 is about the undocumented alternate path that the same audit never exercises.",
4845
+ "last_verified": "2026-06-26"
4742
4846
  }
4743
4847
  }