PheonixAppAPI has visible Encoding Maps
Published Jul 31, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
PheonixAppAPI has visible Encoding Maps
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
This is a kind of moderate issue. The impact is not big for normal users but can be for users who want to secure their code/files/etc.
Potential impact
This is a kind of moderate issue. The impact is not big for normal users but can be for users who want to secure their code/files/etc. The issue is that the map of encoding/decoding languages are visible in code.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Jul 31, 2024 · Last refreshed Nov 3, 2026