{"vulnerability": "CVE-2026-4848", "sightings": [{"uuid": "ad316f7f-59c7-4e28-a1e7-2fd6990f2c08", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-4848", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mhxdb72qij2z", "content": "", "creation_timestamp": "2026-03-26T09:49:52.716744Z"}, {"uuid": "8e971635-b5fd-42f0-b2af-5cb736cebc75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-48489", "type": "seen", "source": "https://bsky.app/profile/symfony.com/post/3mmtax4kuhm2m", "content": "\ud83d\udd10 CVE-2026-48489: Security Firewall Bypass via failure_forward Subrequest\n\u27a1\ufe0f https://symfony.com/blog/cve-2026-48489-security-firewall-bypass-via-failure-forward-subrequest", "creation_timestamp": "2026-05-27T10:03:46.196289Z"}, {"uuid": "4c545453-1826-44a9-ba1a-1124e1457ba9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48489", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mmtq4e3x7q2h", "content": "\ud83d\udd17 CVE : CVE-2026-48489, CVE-2026-48736, CVE-2026-48747, CVE-2026-48760, CVE-2026-48761, CVE-2026-48784", "creation_timestamp": "2026-05-27T14:35:08.068108Z"}, {"uuid": "bb017b2c-f7ca-4159-a957-e661d3cc045e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48480", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mnic4kb5ip2y", "content": "CVE-2026-48480 - netty-incubator-codec-ohttp OHttpVersionChunkDraft's Missing Final-Chunk Enforcement Leads to Undetected Stream Truncation\nCVE ID : CVE-2026-48480\n \n Published : June 4, 2026, 5:39 p.m. | 53\u00a0minutes ago\n \n Description : The netty incubator codec.bhttp is a jav...", "creation_timestamp": "2026-06-04T18:50:36.560942Z"}, {"uuid": "899899c6-21b8-4aa7-ba6c-82f4455f6af6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48488", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mns6uv44732s", "content": "CVE-2026-48488 - phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing\nCVE ID : CVE-2026-48488\n \n Published : June 8, 2026, 4:16 p.m. | 17\u00a0minutes ago\n \n Description : phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed ...", "creation_timestamp": "2026-06-08T17:19:15.967805Z"}, {"uuid": "af3d444f-9da9-4d9a-8750-c6a90edc3542", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48485", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mo3um2z5le2f", "content": "CVE-2026-48485 - Quest Bot: Stored warn reasons can still trigger bot-powered mass mentions through `/warns`.\nCVE ID : CVE-2026-48485\n \n Published : 2026\u5e746\u670812\u65e5 11:53 | 1\u00a0\u5c0f\u65f6\uff0c29\u00a0\u5206\u949f ago\n \n Description : Quest Bot is an opensource Discord Bot. Prior to version 1.1.6, the latest re...", "creation_timestamp": "2026-06-12T13:41:59.725019Z"}, {"uuid": "16b7ccd8-cb87-4099-9ecd-fb11e46ebf87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48488", "type": "seen", "source": "https://gist.github.com/alon710/e0871f429bd0cd1c539be9054ab3870b", "content": "# CVE-2026-48488: CVE-2026-48488: Weak Cryptographic Hash (SHA-1) Usage for Attachment Encryption Keys in phpMyFAQ\n\n> **CVSS Score:** 2.7\n> **Published:** 2026-06-23\n> **Full Report:** https://cvereports.com/reports/CVE-2026-48488\n\n## Summary\nPrior to version 4.1.4, phpMyFAQ used the cryptographically broken SHA-1 algorithm to hash custom attachment encryption keys stored in the database. Attackers with database access can recover these plaintext keys through offline brute-force attacks and subsequently decrypt sensitive file attachments.\n\n## TL;DR\nphpMyFAQ stored SHA-1 hashes of custom attachment encryption keys in the database. Attackers gaining database read access can rapidly crack these hashes offline to decrypt sensitive attachments.\n\n## Technical Details\n\n- **CWE ID**: CWE-328 (Use of Weak Hash)\n- **Attack Vector**: Network (AV:N)\n- **CVSS v4.0**: 2.7 (Low)\n- **EPSS Score**: 0.00182\n- **Impact**: Low (Confidentiality compromise of encrypted attachments)\n- **Exploit Status**: None\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- phpMyFAQ\n- **phpMyFAQ**: < 4.1.4 (Fixed in: `4.1.4`)\n\n## Mitigation\n\n- Upgrade phpMyFAQ to version 4.1.4 or higher\n- Manually sanitize historical SHA-1 hashes from the database\n- Rotate attachment encryption keys if a database breach has occurred\n\n**Remediation Steps:**\n1. Upgrade the phpMyFAQ application code to version 4.1.4 or later\n2. Run the SQL command to clear legacy columns: UPDATE faqattachment SET password_hash = NULL;\n3. Audit database read access logs to ensure no unauthorized access has occurred\n\n## References\n\n- [GHSA-58fg-62fg-3fcj: Weak Cryptography in phpMyFAQ Attachment Keys](https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-58fg-62fg-3fcj)\n- [Fix Commit: Remove password hashing and password property from Attachment](https://github.com/thorsten/phpMyFAQ/commit/1aa9be6f8a2fa5c527c983826205229fc3129718)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-48488) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-06-24T06:12:05.000000Z"}, {"uuid": "34ce8e50-5964-4ce8-a26b-bfe41c2baefa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48480", "type": "seen", "source": "https://gist.github.com/alon710/ce3b2aa80a723c8da0f2d02f44d2e2db", "content": "# CVE-2026-48480: CVE-2026-48480: Undetected Stream Truncation in netty-incubator-codec-ohttp\n\n> **CVSS Score:** 6.6\n> **Published:** 2026-06-23\n> **Full Report:** https://cvereports.com/reports/CVE-2026-48480\n\n## Summary\nThe Netty incubator codec for Oblivious HTTP (OHTTP) fails to verify that a cryptographically signed final chunk is received before the outer HTTP body terminates. This missing validation allows an on-path adversary to truncate chunked-OHTTP messages cleanly at a non-final chunk boundary, leading to undetected data truncation and compromising message integrity. The vulnerability affects multiple versions of the maven package io.netty.incubator:netty-incubator-codec-ohttp prior to 0.0.22.Final.\n\n## TL;DR\nAn on-path adversary can cleanly truncate a chunked-OHTTP stream at a non-final chunk boundary, bypassing integrity checks without triggering decryption errors or application exceptions.\n\n## Technical Details\n\n- **CWE ID**: CWE-325\n- **Vulnerability Type**: Missing Cryptographic Step\n- **Attack Vector**: Network (AV:N)\n- **CVSS v4.0**: 6.6 (Medium)\n- **EPSS Score**: 0.00167\n- **Exploit Status**: PoC / Test-Only\n- **CISA KEV Status**: Not Listed\n\n## Affected Systems\n\n- io.netty.incubator:netty-incubator-codec-ohttp\n- **netty-incubator-codec-ohttp**: < 0.0.22.Final (Fixed in: `0.0.22.Final`)\n\n## Mitigation\n\n- Upgrade netty-incubator-codec-ohttp to version 0.0.22.Final or higher.\n- Implement log monitoring for CorruptedFrameException indicating OHTTP stream truncation.\n- Enforce strict validation of message lengths at the application layer where possible.\n\n**Remediation Steps:**\n1. Identify all Maven dependencies referencing io.netty.incubator:netty-incubator-codec-ohttp.\n2. Update the dependency version in pom.xml to 0.0.22.Final.\n3. Rebuild and redeploy the affected applications.\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-48480) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-06-24T06:42:05.000000Z"}]}