JLSEC-2026-41
- Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-41.md
- Import Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-41.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/JLSEC-2026-41
- Upstream
- Published
- 2026-04-03T13:27:15.647Z
- Modified
- 2026-07-18T18:25:35.991193585Z
- Severity
-
- 5.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N CVSS Calculator
- Summary
- [none]
- Details
-
Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.
- Database specific
{ "sources": [ { "published": "2023-06-09T19:15:09.313Z", "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2455", "imported": "2026-07-17T21:48:57.229Z", "id": "CVE-2023-2455", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2023-2455", "database_specific": { "status": "Modified" }, "modified": "2026-06-17T05:52:37.740Z" } ], "license": "CC-BY-4.0" }- References