π¨ CVE-2026-123579
DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.
π@cveNotify
DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.
π@cveNotify
GitHub
DNSSEC validation accepts bogus positive response with wildcard expansion
DNSSEC validation does not sufficiently distinguish between NODATA respones and positive responses with wildcard expansion. If a query is made that should result in a NODATA response, and the zone ...
π¨ CVE-2026-123583
The recursive resolver in Hickory DNS hickory-recursor 0.25.0 through 0.25.2 and hickory-resolver 0.26.0 before 0.26.2 does not apply out-of-bailiwick filtering to negative responses. Attackers able to supply crafted negative responses can include out-of-bailiwick records to facilitate cache poisoning and more easily exploit other DNSSEC verification flaws.
π@cveNotify
The recursive resolver in Hickory DNS hickory-recursor 0.25.0 through 0.25.2 and hickory-resolver 0.26.0 before 0.26.2 does not apply out-of-bailiwick filtering to negative responses. Attackers able to supply crafted negative responses can include out-of-bailiwick records to facilitate cache poisoning and more easily exploit other DNSSEC verification flaws.
π@cveNotify
GitHub
Out-of-bailiwick filtering is not applied to negative responses
**Reporter:** Qifan Zhang, Palo Alto Networks
Hickory DNS's recursive resolver does not perform out-of-bailiwick filtering on negative responses. Bailiwick filtering is a useful mitigation f...
Hickory DNS's recursive resolver does not perform out-of-bailiwick filtering on negative responses. Bailiwick filtering is a useful mitigation f...
π¨ CVE-2026-123587
The DNSSEC validation in the Hickory DNS hickory-net crate 0.26.0 before 0.26.2 identifies wraparound NSEC records by comparing the next domain name to an SOA record in the response, accepting that SOA even if it fails validation. Attackers who can supply DNS responses can combine a genuine NSEC record and its RRSIG with a crafted SOA record to forge nonexistence of any RRset.
π@cveNotify
The DNSSEC validation in the Hickory DNS hickory-net crate 0.26.0 before 0.26.2 identifies wraparound NSEC records by comparing the next domain name to an SOA record in the response, accepting that SOA even if it fails validation. Attackers who can supply DNS responses can combine a genuine NSEC record and its RRSIG with a crafted SOA record to forge nonexistence of any RRset.
π@cveNotify
GitHub
DNSSEC nonexistence forgery via incorrect handling of wraparound NSEC records
DNSSEC verification did not handle wraparound NSEC records correctly, i.e. NSEC records for which the next domain name is the zone's apex. The existing routine for testing whether an NSEC recor...
π¨ CVE-2026-123591
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 fail to verify, per RFC 6840 Β§4.4, that an NSEC or NSEC3 record denying a DS RRset also proves the delegation's NS record exists. Attackers can reuse child-side NSEC or NSEC3 records to fake an insecure delegation and forge child-zone records.
π@cveNotify
Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 fail to verify, per RFC 6840 Β§4.4, that an NSEC or NSEC3 record denying a DS RRset also proves the delegation's NS record exists. Attackers can reuse child-side NSEC or NSEC3 records to fake an insecure delegation and forge child-zone records.
π@cveNotify
GitHub
DNSSEC validation is missing RFC 6840 Β§4.4 checks
When an insecure delegation is validated, RFC 6840 Β§4.4 says that the NSEC or NSEC3 record used to prove that no DS record exists must also prove that the delegation's NS record does exist or c...
π¨ CVE-2026-123595
Hickory DNS hickory-proto 0.25 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw in the validating recursor's NSEC3 handler, which matches the closest encloser by hash alone without checking the type bitmap and so accepts parent-side ancestor-delegation NSEC3 records as proof of nonexistence. An attacker who delivers one response built from genuinely signed parent NSEC3 records can cause NXDOMAIN or NODATA to be cached with AD=1, denying resolution of existing names at and below the zone cut.
π@cveNotify
Hickory DNS hickory-proto 0.25 through 0.26.0-alpha.1 and hickory-net 0.26.0-beta.1 before 0.26.2 contain a DNSSEC validation flaw in the validating recursor's NSEC3 handler, which matches the closest encloser by hash alone without checking the type bitmap and so accepts parent-side ancestor-delegation NSEC3 records as proof of nonexistence. An attacker who delivers one response built from genuinely signed parent NSEC3 records can cause NXDOMAIN or NODATA to be cached with AD=1, denying resolution of existing names at and below the zone cut.
π@cveNotify
GitHub
ancestor-delegation NSEC3 accepted as proof of nonexistence at and below the zone cut
The validating recursor's NSEC3 handler does not implement the RFC 6840 Β§4.1 / RFC 5155 Β§8.3 "ancestor delegation" exclusion. The closest-encloser match in the NXDOMAIN proof selects ...
π¨ CVE-2026-123599
Hickory DNS hickory-proto before 0.26.0-beta.1 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because verify_rrsets() ignores DNS class when partitioning RRsets, so non-IN records skip signature verification yet are marked secure when the IN records verify. Attackers able to supply DNS responses can include forged CH or HS class records, including DS records, to authenticate any DNSKEY and forge child zone responses.
π@cveNotify
Hickory DNS hickory-proto before 0.26.0-beta.1 and hickory-net before 0.26.2 contain a DNSSEC validation bypass because verify_rrsets() ignores DNS class when partitioning RRsets, so non-IN records skip signature verification yet are marked secure when the IN records verify. Attackers able to supply DNS responses can include forged CH or HS class records, including DS records, to authenticate any DNSKEY and forge child zone responses.
π@cveNotify
GitHub
DNSSEC validation ignores bogus records with a DNS class other than IN
**Reporter:** Qifan Zhang, Palo Alto Networks
The `verify_rrsets()` method ignores class when partitioning records into RRsets, and records with a class other than IN get filtered out before sig...
The `verify_rrsets()` method ignores class when partitioning records into RRsets, and records with a class other than IN get filtered out before sig...
π¨ CVE-2026-123603
hickory-proto and hickory-resolver 0.26.0 before 0.26.2, hickory-server 0.25.0-alpha.1 before 0.26.2, and hickory-recursor 0.25.0-alpha.3 through 0.26.0-alpha.1 fail to canonicalize IPv4-mapped IPv6 addresses when checking deny_answers, deny_server, or AccessControlSet rules. Attackers can use IPv4-mapped addresses to evade answer filtering, trigger queries to denied nameservers, or reach hickory-server library deployments on dual-stack IPv6 sockets from denied clients.
π@cveNotify
hickory-proto and hickory-resolver 0.26.0 before 0.26.2, hickory-server 0.25.0-alpha.1 before 0.26.2, and hickory-recursor 0.25.0-alpha.3 through 0.26.0-alpha.1 fail to canonicalize IPv4-mapped IPv6 addresses when checking deny_answers, deny_server, or AccessControlSet rules. Attackers can use IPv4-mapped addresses to evade answer filtering, trigger queries to denied nameservers, or reach hickory-server library deployments on dual-stack IPv6 sockets from denied clients.
π@cveNotify
GitHub
Missing IPv4-Mapped IPv6 address canonicalization
When checking IP addresses against a resolver's answer address filter, a recursor's do not query filters, or a server's client allow list, IPv4-Mapped-IPv6 addresses were not canonicali...
π¨ CVE-2026-123607
Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net before 0.26.1 contain an unbounded loop vulnerability in DnssecDnsHandle NSEC3 closest-encloser proof validation when the SOA owner is not an ancestor of the QNAME. Upstream attackers can return NoData or NXDomain responses with a cross-zone SOA record to panic debug builds or exhaust memory in release builds.
π@cveNotify
Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net before 0.26.1 contain an unbounded loop vulnerability in DnssecDnsHandle NSEC3 closest-encloser proof validation when the SOA owner is not an ancestor of the QNAME. Upstream attackers can return NoData or NXDomain responses with a cross-zone SOA record to panic debug builds or exhaust memory in release builds.
π@cveNotify
GitHub
NSEC3 closest-encloser proof validation enters unbounded loop on cross-zone responses
The NSEC3 closest-encloser proof validation in `hickory-proto`'s (0.25.0-alpha.3 ... 0.25.2) and `hickory-net`'s (0.26.0-alpha.1 .. 0.26.0) `DnssecDnsHandle` walks from the QNAME up to the...
π¨ CVE-2026-123611
rustls before 0.23.46 contains a key exchange downgrade vulnerability that allows network attackers to poison the per-server-name key-exchange group record via an unauthenticated ServerHello. Attackers can answer one connection with a ServerHello selecting X25519, causing later ClientHellos to send only classical shares and lose post-quantum confidentiality.
π@cveNotify
rustls before 0.23.46 contains a key exchange downgrade vulnerability that allows network attackers to poison the per-server-name key-exchange group record via an unauthenticated ServerHello. Attackers can answer one connection with a ServerHello selecting X25519, causing later ClientHellos to send only classical shares and lose post-quantum confidentiality.
π@cveNotify
GitHub
An unauthenticated ServerHello poisons the per-name key-exchange record, so later ClientHellos carry only a classical X25519 share
## Summary
The client records the server-selected key-exchange group per server name when it processes the ServerHello, before the server is authenticated. A network attacker can answer one conn...
The client records the server-selected key-exchange group per server name when it processes the ServerHello, before the server is authenticated. A network attacker can answer one conn...
π¨ CVE-2026-123615
imgproxy 3.3.0 before 4.0.17 contains an out-of-bounds heap read and write in the ICO loader's BMP header reconstruction (vips_foreign_load_ico_header in vips/icoload.c) when an ICO entry declares a tiny data size, causing unvalidated header fields to be read and written past the allocated buffer. Unauthenticated remote attackers can supply a crafted ICO image to corrupt adjacent heap chunk metadata, triggering a glibc abort that crashes the worker.
π@cveNotify
imgproxy 3.3.0 before 4.0.17 contains an out-of-bounds heap read and write in the ICO loader's BMP header reconstruction (vips_foreign_load_ico_header in vips/icoload.c) when an ICO entry declares a tiny data size, causing unvalidated header fields to be read and written past the allocated buffer. Unauthenticated remote attackers can supply a crafted ICO image to corrupt adjacent heap chunk metadata, triggering a glibc abort that crashes the worker.
π@cveNotify
GitHub
Out-of-bounds heap read/write in ICO loader BMP header reconstruction allows unauthenticated remote worker crash
### Summary
Out-of-bounds heap write in imgproxy's ICO loader (`vips/icoload.c`): when the ICO entry's image data buffer is small, the loader's BMP-header-reconstruction writes land ...
Out-of-bounds heap write in imgproxy's ICO loader (`vips/icoload.c`): when the ICO entry's image data buffer is small, the loader's BMP-header-reconstruction writes land ...
π¨ CVE-2026-124326
A flaw has been found in DataLinkDC Dinky up to 1.2.5. Impacted is the function file.getOriginalFilename of the file CatalogueController.java of the component Catalogue Upload. Executing a manipulation of the argument filename can lead to path traversal. The attack can be executed remotely. The exploit has been published and may be used. The researcher claims to have submitted a GHSA on the repository of the project.
π@cveNotify
A flaw has been found in DataLinkDC Dinky up to 1.2.5. Impacted is the function file.getOriginalFilename of the file CatalogueController.java of the component Catalogue Upload. Executing a manipulation of the argument filename can lead to path traversal. The attack can be executed remotely. The exploit has been published and may be used. The researcher claims to have submitted a GHSA on the repository of the project.
π@cveNotify
GitHub
GitHub - DataLinkDC/dinky: Dinky is a real-time data development platform based on Apache Flink, enabling agile data developmentβ¦
Dinky is a real-time data development platform based on Apache Flink, enabling agile data development, deployment and operation. - DataLinkDC/dinky
π¨ CVE-2026-124331
A vulnerability was identified in Jinher OA C6. This impacts an unknown function of the file /C6/JHSoft.Web.Project/OfficeReadOnly/ProjectAfficheManage.aspx. Such manipulation of the argument ProjID leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
π@cveNotify
A vulnerability was identified in Jinher OA C6. This impacts an unknown function of the file /C6/JHSoft.Web.Project/OfficeReadOnly/ProjectAfficheManage.aspx. Such manipulation of the argument ProjID leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
π@cveNotify
GitHub
Jinher OA SQL Injection Vulnerability Report Β· Issue #2 Β· wangpenglei11/Submit
Jinher OA SQL Injection Vulnerability Report AFFECTED PRODUCT Product: Jinher OA (Jhsoft OA) Affected Component: /C6/JHSoft.Web.Project/OfficeReadOnly/ProjectAfficheManage.aspx VENDOR INFORMATION V...
π¨ CVE-2026-124425
Parse Server 8.6.109 before 8.6.116 and 9.10.6-alpha.1 before 9.10.7-alpha.2 contains an information disclosure vulnerability in which create or update responses mark fields as deleted based on stored values the caller cannot read. Attackers with write but not read access to an object can inspect these markers to infer whether protected fields are set.
π@cveNotify
Parse Server 8.6.109 before 8.6.116 and 9.10.6-alpha.1 before 9.10.7-alpha.2 contains an information disclosure vulnerability in which create or update responses mark fields as deleted based on stored values the caller cannot read. Attackers with write but not read access to an object can inspect these markers to infer whether protected fields are set.
π@cveNotify
GitHub
Save response reveals whether a field is stored to a caller without read access
### Impact
A client that can create or update an object but cannot read it receives a save response that marks fields as deleted. Whether a field is marked depends on stored values that the client...
A client that can create or update an object but cannot read it receives a save response that marks fields as deleted. Whether a field is marked depends on stored values that the client...
π¨ CVE-2026-124429
Craft CMS from 5.0.0 before 5.11.2 contains a privilege escalation vulnerability that allows unauthenticated public registrants to reclaim deactivated non-admin accounts while retaining their direct permissions. Attackers can register using a deactivated account, set a new password, and inherit permissions stored in userpermissions_users, enabling privileged account takeover when email verification is disabled.
π@cveNotify
Craft CMS from 5.0.0 before 5.11.2 contains a privilege escalation vulnerability that allows unauthenticated public registrants to reclaim deactivated non-admin accounts while retaining their direct permissions. Attackers can register using a deactivated account, set a new password, and inherit permissions stored in userpermissions_users, enabling privileged account takeover when email verification is disabled.
π@cveNotify
GitHub
Public registration inherits direct permissions from a deactivated account
Craft CMS allows an unauthenticated public registrant to reclaim a deactivated non-admin account while retaining all direct permissions previously assigned to that account.
The 5.10.11 fix for G...
The 5.10.11 fix for G...
π¨ CVE-2026-124433
phpMyFAQ before 4.1.11 contains an insufficient authorization vulnerability that allows delegated administrators holding only GROUP_DELETE permission to delete higher-privileged groups. Attackers can submit a target group_list_select value to /admin/group/confirm and then /admin/group/delete to remove privileged groups, their memberships, and permission mappings.
π@cveNotify
phpMyFAQ before 4.1.11 contains an insufficient authorization vulnerability that allows delegated administrators holding only GROUP_DELETE permission to delete higher-privileged groups. Attackers can submit a target group_list_select value to /admin/group/confirm and then /admin/group/delete to remove privileged groups, their memberships, and permission mappings.
π@cveNotify
GitHub
Insufficient Authorization Allows a Delegated Group Administrator to Delete Higher-Privileged Groups
### Summary
phpMyFAQ 4.1.10 with `security.permLevel=medium` allows an authenticated, non-SuperAdmin account holding only the delegated `GROUP_DELETE` (`delgroup`) permission to delete a group c...
phpMyFAQ 4.1.10 with `security.permLevel=medium` allows an authenticated, non-SuperAdmin account holding only the delegated `GROUP_DELETE` (`delgroup`) permission to delete a group c...
π¨ CVE-2026-124437
Scriban before 7.5.3 contains a resource exhaustion vulnerability that allows untrusted template authors to exhaust memory and CPU because builtins like math.format, regex.replace and string.escape skip the LimitToString allocation guard. Attackers can submit small templates using huge format precision specifiers, shared-structure array comparison, BigInteger multiplication or exponential function recursion that ignore LoopLimit and CancellationToken, crashing or stalling multi-tenant hosts.
π@cveNotify
Scriban before 7.5.3 contains a resource exhaustion vulnerability that allows untrusted template authors to exhaust memory and CPU because builtins like math.format, regex.replace and string.escape skip the LimitToString allocation guard. Attackers can submit small templates using huge format precision specifiers, shared-structure array comparison, BigInteger multiplication or exponential function recursion that ignore LoopLimit and CancellationToken, crashing or stalling multi-tenant hosts.
π@cveNotify
GitHub
Memory and CPU exhaustion under default limits: string builtins skip the LimitToString allocation guard, and array comparison /β¦
**Severity:** High β CVSS 3.1 **7.5** `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`
- AV:N / PR:N / UI:N / AC:L: a template under 100 characters, default `TemplateContext`, nothing exposed by the ...
- AV:N / PR:N / UI:N / AC:L: a template under 100 characters, default `TemplateContext`, nothing exposed by the ...
π¨ CVE-2026-124445
OpenEMR from 7.0.1 before 8.4.0 contains a flaw in src/Common/Auth/OneTimeAuth.php that ignores the enforce_onetime_use and max_access_count flags, never revokes consumed service_auth tokens, and checks login_pin without rate limiting or strict comparison. Attackers holding a captured token can replay it or brute-force the PIN to open patient-portal sessions exposing PHI.
π@cveNotify
OpenEMR from 7.0.1 before 8.4.0 contains a flaw in src/Common/Auth/OneTimeAuth.php that ignores the enforce_onetime_use and max_access_count flags, never revokes consumed service_auth tokens, and checks login_pin without rate limiting or strict comparison. Attackers holding a captured token can replay it or brute-force the PIN to open patient-portal sessions exposing PHI.
π@cveNotify
GitHub
OpenEMR OneTimeAuth token replay and PIN brute force
# OpenEMR OneTimeAuth token replay and PIN brute force
**CWE:** CWE-307 (Improper Restriction of Excessive Authentication Attempts), with CWE-613 (Insufficient Session Expiration) on the token-r...
**CWE:** CWE-307 (Improper Restriction of Excessive Authentication Attempts), with CWE-613 (Insufficient Session Expiration) on the token-r...
π¨ CVE-2026-124449
OpenEMR before 8.4.0 contains a missing authorization vulnerability in FHIR Media/:uuid and QuestionnaireResponse read routes that skip ACL checks. Non-patient API tokens lacking OpenEMR ACLs can request resources by uuid, bypassing compartment filtering to read any patient's documents and questionnaire responses.
π@cveNotify
OpenEMR before 8.4.0 contains a missing authorization vulnerability in FHIR Media/:uuid and QuestionnaireResponse read routes that skip ACL checks. Non-patient API tokens lacking OpenEMR ACLs can request resources by uuid, bypassing compartment filtering to read any patient's documents and questionnaire responses.
π@cveNotify
GitHub
FHIR Media/:uuid and QuestionnaireResponse read routes skip both ACL mechanisms
## Relationship to CVE-2026-25164
I want to lead with this, because this finding is a residual rather than a new discovery.
CVE-2026-25164 (GHSA-f64c-h2gh-g3f9, "Document and Insurance R...
I want to lead with this, because this finding is a residual rather than a new discovery.
CVE-2026-25164 (GHSA-f64c-h2gh-g3f9, "Document and Insurance R...
π¨ CVE-2026-124453
OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in portal/lib/persist.php that allows authenticated portal patients to write settings for other patients. Attackers can modify the setting_patient parameter in a JSON POST request to another patient's PID, altering that patient's portal settings such as the portal theme.
π@cveNotify
OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in portal/lib/persist.php that allows authenticated portal patients to write settings for other patients. Attackers can modify the setting_patient parameter in a JSON POST request to another patient's PID, altering that patient's portal settings such as the portal theme.
π@cveNotify
GitHub
IDOR - Portal Patient Settings Written for Arbitrary PID
# IDOR - Portal Patient Settings Written for Arbitrary PID
**Severity:** Low/Medium
**CWE:** CWE-639 (Authorization Bypass Through User-Controlled Key)
**File:** `portal/lib/persist.php:53β55`...
**Severity:** Low/Medium
**CWE:** CWE-639 (Authorization Bypass Through User-Controlled Key)
**File:** `portal/lib/persist.php:53β55`...
π¨ CVE-2026-124458
OpenEMR before 8.4.0 contains an authorization bypass vulnerability in the FHIR GET /fhir/Person/:uuid route that allows patient-portal users to read any staff member's demographics by bypassing compartment enforcement. Attackers holding a patient SMART token with patient/Person.read can harvest staff Person UUIDs from Appointment references to retrieve names, home addresses, phone numbers, and personal emails.
π@cveNotify
OpenEMR before 8.4.0 contains an authorization bypass vulnerability in the FHIR GET /fhir/Person/:uuid route that allows patient-portal users to read any staff member's demographics by bypassing compartment enforcement. Attackers holding a patient SMART token with patient/Person.read can harvest staff Person UUIDs from Appointment references to retrieve names, home addresses, phone numbers, and personal emails.
π@cveNotify
GitHub
FHIR Patient Compartment bypass on Person: a patient SMART token can read any staff member's PII
# FHIR Patient Compartment bypass on Person: a patient SMART token can read any staff member's PII
## Summary
`GET /fhir/Person/:uuid` does not enforce the patient compartment for patient-s...
## Summary
`GET /fhir/Person/:uuid` does not enforce the patient compartment for patient-s...
π¨ CVE-2026-124462
OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in OnsiteDocumentController::Query() that allows authenticated portal patients to bypass the lowercase pid authorization guard by supplying a capitalised Pid parameter. Attackers can request the api/onsitedocuments endpoint with Pid set to another patient's id to overwrite the session-pinned criteria and read other patients' onsite documents containing PHI.
π@cveNotify
OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in OnsiteDocumentController::Query() that allows authenticated portal patients to bypass the lowercase pid authorization guard by supplying a capitalised Pid parameter. Attackers can request the api/onsitedocuments endpoint with Pid set to another patient's id to overwrite the session-pinned criteria and read other patients' onsite documents containing PHI.
π@cveNotify
GitHub
Cross-patient PHI disclosure (IDOR) in patient portal via case-sensitive `Pid` parameter β bypass of the portal `pid` authorizationβ¦
## Summary
The patient portal pins the patient id to the authenticated session and adds a guard in `portal/patient/index.php` that rejects requests where lowercase `pid` or `patientId` differ from...
The patient portal pins the patient id to the authenticated session and adds a guard in `portal/patient/index.php` that rejects requests where lowercase `pid` or `patientId` differ from...